More than 5,500 GitHub repositories — 5,561, by SafeDep's count — were infected with malware on May 18, 2026, in a supply chain attack called Megalodon. Attackers pushed 5,718 malicious commits across a six-hour window using two email addresses, injecting rogue GitHub Actions workflows designed to steal credentials, AWS keys, SSH private keys, API tokens, and dozens of other secrets from CI environments.
They got in with stolen personal access tokens and deploy keys, pushing straight to master with no pull request. Hudson Rock matched more than a third of the usernames behind the affected repositories to machines infected by infostealer malware. The workflows sent everything to 216.126.225[.]129.
The attack surfaced when poisoned Tiledesk npm versions 2.18.6 through 2.18.12 were published May 19–21. The maintainer unknowingly published from a poisoned source — the attacker never touched the npm account, only the GitHub repo. A dormant backdoor was also planted, triggerable later via the GitHub API using stolen tokens. Rotate any token that can reach your repositories, and check for workflow files nobody on your team wrote.
Source: SecurityWeek
More than 5,500 GitHub repositories — 5,561, by SafeDep's count — were infected with malware on May 18, 2026, in a supply chain attack called Megalodon. Attackers pushed 5,718 malicious commits across a six-hour window using two email addresses, injecting rogue GitHub Actions workflows designed to steal credentials, AWS keys, SSH private keys, API tokens, and dozens of other secrets from CI environments.
They got in with stolen personal access tokens and deploy keys, pushing straight to master with no pull request. Hudson Rock matched more than a third of the usernames behind the affected repositories to machines infected by infostealer malware. The workflows sent everything to 216.126.225[.]129.
The attack surfaced when poisoned Tiledesk npm versions 2.18.6 through 2.18.12 were published May 19–21. The maintainer unknowingly published from a poisoned source — the attacker never touched the npm account, only the GitHub repo. A dormant backdoor was also planted, triggerable later via the GitHub API using stolen tokens. Rotate any token that can reach your repositories, and check for workflow files nobody on your team wrote.
Source: SecurityWeek
Microsoft disclosed a zero-day in Exchange (CVE-2026-42897) on Thursday, May 14, and five days later customers are still waiting for a patch. CISA added it to the Known Exploited Vulnerabilities catalog the next day, giving federal agencies until June 5 to act.
The flaw sits in Outlook Web Access on on-premises Exchange — Exchange Online isn't affected — and allows spoofing over a network via cross-site scripting. Attackers send a specially crafted email that runs arbitrary JavaScript when it's opened in OWA. It affects Exchange Server 2016, 2019 and Subscription Edition. Microsoft scored it 8.1; NVD rates the same flaw 6.1, medium severity.
Security experts warn successful attacks could compromise mailboxes, steal session tokens, and enable business email compromise or ransomware. Microsoft's two temporary mitigations are the Exchange Emergency Mitigation Service, which it recommends and which has been on by default since 2021, and the updated Exchange On-Premises Mitigation Tool — expect OWA Print Calendar and OWA Light to break.
Updated August 13, 2026: Microsoft patched this on June 9 — Exchange SE build 15.2.2562.43 (KB5094139), 2019 CU15 15.2.1748.46, 2019 CU14 15.2.1544.41, and 2016 CU23 15.1.2507.69. The 2016 and 2019 updates are only available to organizations enrolled in Extended Security Updates, and Microsoft says to leave the mitigation in place after installing.
Source: Dark Reading
Microsoft disclosed a zero-day in Exchange (CVE-2026-42897) on Thursday, May 14, and five days later customers are still waiting for a patch. CISA added it to the Known Exploited Vulnerabilities catalog the next day, giving federal agencies until June 5 to act.
The flaw sits in Outlook Web Access on on-premises Exchange — Exchange Online isn't affected — and allows spoofing over a network via cross-site scripting. Attackers send a specially crafted email that runs arbitrary JavaScript when it's opened in OWA. It affects Exchange Server 2016, 2019 and Subscription Edition. Microsoft scored it 8.1; NVD rates the same flaw 6.1, medium severity.
Security experts warn successful attacks could compromise mailboxes, steal session tokens, and enable business email compromise or ransomware. Microsoft's two temporary mitigations are the Exchange Emergency Mitigation Service, which it recommends and which has been on by default since 2021, and the updated Exchange On-Premises Mitigation Tool — expect OWA Print Calendar and OWA Light to break.
Updated August 13, 2026: Microsoft patched this on June 9 — Exchange SE build 15.2.2562.43 (KB5094139), 2019 CU15 15.2.1748.46, 2019 CU14 15.2.1544.41, and 2016 CU23 15.1.2507.69. The 2016 and 2019 updates are only available to organizations enrolled in Extended Security Updates, and Microsoft says to leave the mitigation in place after installing.
Source: Dark Reading
Cybercriminals have already cloned the Shai-Hulud malware, days after TeamPCP published its source code on GitHub under an MIT License on May 12. The original worm first hit the open source ecosystem in September 2025 — and again that November — stealing credentials and API keys from developers to spread through NPM packages.
Ox Security discovered four malicious NPM packages: 'chalk-tempalte', a near-unchanged clone of the leaked worm that typo-squats chalk-template; 'axois-utils' and '@deadcode09284814/axios-util', both going after Axios users; and 'color-style-utils'. Together they were pulling around 2,678 downloads a week. One of them, 'axois-utils', drops Phantom Bot — a Go-based DDoS botnet that presses infected machines into HTTP, TCP and UDP floods.
All four were still downloadable from NPM when researchers published. If you've installed any of them: uninstall, rotate your keys, delete any malicious IDE or coding-agent configs left behind, and check your GitHub account for a repo named 'A Mini Sha1-Hulud has Appeared'. Ox Security expects this is only the first phase of a wider wave.
Source: Security Week
Cybercriminals have already cloned the Shai-Hulud malware, days after TeamPCP published its source code on GitHub under an MIT License on May 12. The original worm first hit the open source ecosystem in September 2025 — and again that November — stealing credentials and API keys from developers to spread through NPM packages.
Ox Security discovered four malicious NPM packages: 'chalk-tempalte', a near-unchanged clone of the leaked worm that typo-squats chalk-template; 'axois-utils' and '@deadcode09284814/axios-util', both going after Axios users; and 'color-style-utils'. Together they were pulling around 2,678 downloads a week. One of them, 'axois-utils', drops Phantom Bot — a Go-based DDoS botnet that presses infected machines into HTTP, TCP and UDP floods.
All four were still downloadable from NPM when researchers published. If you've installed any of them: uninstall, rotate your keys, delete any malicious IDE or coding-agent configs left behind, and check your GitHub account for a repo named 'A Mini Sha1-Hulud has Appeared'. Ox Security expects this is only the first phase of a wider wave.
Source: Security Week
A Windows privilege escalation flaw called "MiniPlasma" has surfaced with public exploit code on GitHub, published May 13, 2026 — one day after May's Patch Tuesday. Researcher Nightmare-Eclipse says Microsoft never properly fixed a bug James Forshaw of Google Project Zero reported in September 2020 and Microsoft closed that December.
There's no new CVE: it still tracks under the 2020 one, CVE-2020-17103, rated 7.8 High by NVD and 7.0 by Microsoft. The flaw is in the Cloud Files Mini Filter driver (cldflt.sys), where a missing access check lets a standard user win a race to create registry keys in the .DEFAULT hive and take SYSTEM on fully patched machines.
The researcher reports it working on every Windows version he tested, and it's confirmed on Windows 11 with the May 2026 updates — but it fails on the latest Windows 11 Insider Preview Canary build, and because it's a race condition, reliability varies. Since cldflt underpins OneDrive and other cloud storage, the vulnerable code sits on most Windows installs.
The repository passed 390 stars within days. Until Microsoft ships a fix, application control and EDR monitoring of the affected registry keys are the only containment available — neither closes the hole.
Updated August 13, 2026: Microsoft patched MiniPlasma on June 9, 2026 in its June Patch Tuesday — still under CVE-2020-17103, six years after first closing it. If you haven't applied it, watch for symbolic links created under HKU.DEFAULT\Software\Policies\Microsoft\CloudFiles\BlockedApps.
Source: Cybersecurity News
A Windows privilege escalation flaw called "MiniPlasma" has surfaced with public exploit code on GitHub, published May 13, 2026 — one day after May's Patch Tuesday. Researcher Nightmare-Eclipse says Microsoft never properly fixed a bug James Forshaw of Google Project Zero reported in September 2020 and Microsoft closed that December.
There's no new CVE: it still tracks under the 2020 one, CVE-2020-17103, rated 7.8 High by NVD and 7.0 by Microsoft. The flaw is in the Cloud Files Mini Filter driver (cldflt.sys), where a missing access check lets a standard user win a race to create registry keys in the .DEFAULT hive and take SYSTEM on fully patched machines.
The researcher reports it working on every Windows version he tested, and it's confirmed on Windows 11 with the May 2026 updates — but it fails on the latest Windows 11 Insider Preview Canary build, and because it's a race condition, reliability varies. Since cldflt underpins OneDrive and other cloud storage, the vulnerable code sits on most Windows installs.
The repository passed 390 stars within days. Until Microsoft ships a fix, application control and EDR monitoring of the affected registry keys are the only containment available — neither closes the hole.
Updated August 13, 2026: Microsoft patched MiniPlasma on June 9, 2026 in its June Patch Tuesday — still under CVE-2020-17103, six years after first closing it. If you haven't applied it, watch for symbolic links created under HKU.DEFAULT\Software\Policies\Microsoft\CloudFiles\BlockedApps.
Source: Cybersecurity News
Instructure, the company behind Canvas learning software, has reached an agreement with the criminals behind a breach it detected on April 29. A second intrusion on May 7 knocked Canvas offline, disrupting around 9,000 institutions across the US, Canada, Australia and the UK. Neither Instructure nor the hackers will say whether money changed hands.
The Shiny Hunters group threatened to publish the data — 3.65 terabytes covering some 275 million users, by its own claim — unless a bitcoin ransom was paid. Usernames, email addresses, course names, enrollment information and messages were taken. Course content, submissions and credentials were not.
Students sitting exams were hit hardest. At Mississippi State University, a ransom note appeared on screens just as students finished a 2,900-word essay, leaving them unsure whether their work had saved; the university postponed some exams so they could recover it.
Instructure says the data was returned, that it received digital confirmation of destruction, and that no student or institution needs to negotiate separately. But dealing with extortionists goes against law enforcement advice and guarantees nothing — when the National Crime Agency hacked LockBit, police found data that victims had already paid to have deleted.
Shiny Hunters claims it had breached Canvas twice before. Instructure separately disclosed a breach in September 2025.
Source: BBC
Instructure, the company behind Canvas learning software, has reached an agreement with the criminals behind a breach it detected on April 29. A second intrusion on May 7 knocked Canvas offline, disrupting around 9,000 institutions across the US, Canada, Australia and the UK. Neither Instructure nor the hackers will say whether money changed hands.
The Shiny Hunters group threatened to publish the data — 3.65 terabytes covering some 275 million users, by its own claim — unless a bitcoin ransom was paid. Usernames, email addresses, course names, enrollment information and messages were taken. Course content, submissions and credentials were not.
Students sitting exams were hit hardest. At Mississippi State University, a ransom note appeared on screens just as students finished a 2,900-word essay, leaving them unsure whether their work had saved; the university postponed some exams so they could recover it.
Instructure says the data was returned, that it received digital confirmation of destruction, and that no student or institution needs to negotiate separately. But dealing with extortionists goes against law enforcement advice and guarantees nothing — when the National Crime Agency hacked LockBit, police found data that victims had already paid to have deleted.
Shiny Hunters claims it had breached Canvas twice before. Instructure separately disclosed a breach in September 2025.
Source: BBC
Instructure has reached an agreement with the hackers behind the Canvas breach — and neither side will say whether money changed hands. It detected unauthorized activity on April 29; a second intrusion on May 7 defaced login portals with an extortion note, knocking Canvas offline and disrupting exams at an estimated 9,000 institutions in the US, Canada, Australia and the UK.
ShinyHunters, which claimed the attack, said it stole 3.5 terabytes and threatened to publish it. Instructure says the data was returned, that it has shred logs confirming destruction, and that no customer will be extorted — the deal covers everyone affected, so no student or institution needs to engage the hackers.
By Instructure's account the stolen data is usernames, email addresses, course names, enrollment information and messages, with course content, submissions and credentials untouched. At Mississippi State, student Aubrey Palmer saw the note appear moments after finishing an exam essay, and the university postponed some exams so students could recover lost work.
Law enforcement agencies worldwide advise against paying — when the National Crime Agency hacked LockBit, police found data victims had already paid to have deleted. It's also not Instructure's first time: the ransom note read "Shiny Hunters has breached Instructure (again)", and the company disclosed a separate breach in September 2025.
Source: BBC
Instructure has reached an agreement with the hackers behind the Canvas breach — and neither side will say whether money changed hands. It detected unauthorized activity on April 29; a second intrusion on May 7 defaced login portals with an extortion note, knocking Canvas offline and disrupting exams at an estimated 9,000 institutions in the US, Canada, Australia and the UK.
ShinyHunters, which claimed the attack, said it stole 3.5 terabytes and threatened to publish it. Instructure says the data was returned, that it has shred logs confirming destruction, and that no customer will be extorted — the deal covers everyone affected, so no student or institution needs to engage the hackers.
By Instructure's account the stolen data is usernames, email addresses, course names, enrollment information and messages, with course content, submissions and credentials untouched. At Mississippi State, student Aubrey Palmer saw the note appear moments after finishing an exam essay, and the university postponed some exams so students could recover lost work.
Law enforcement agencies worldwide advise against paying — when the National Crime Agency hacked LockBit, police found data victims had already paid to have deleted. It's also not Instructure's first time: the ransom note read "Shiny Hunters has breached Instructure (again)", and the company disclosed a separate breach in September 2025.
Source: BBC
Day two of Pwn2Own Berlin 2026 saw hackers unleash devastating attacks on enterprise software and AI tools, adding $385,750 in bug bounties to bring the total to $908,750.
Orange Tsai from DEVCORE stole the show with a brutal Microsoft Exchange exploit, chaining three vulnerabilities to achieve remote code execution with SYSTEM privileges. The attack earned $200,000 and highlights Exchange's role as a critical enterprise target.
Security researchers also escalated privileges on Windows 11 through an integer overflow bug — worth $7,500, next to Exchange's $200,000 — and hit multiple AI coding platforms including Cursor IDE and OpenAI Codex. These AI tools are becoming prime targets due to their access to source code and developer workflows.
DEVCORE leads the competition on 40.5 Master of Pwn points and $405,000 in winnings, and the final day promises more zero-day discoveries. Every vendor now has 90 days to ship a fix before ZDI publishes the details.
Updated August 13, 2026: Pwn2Own Berlin closed on May 16 with $1,298,250 paid out for 47 zero-days, and DEVCORE took Master of Pwn on 50.5 points and $505,000.
Source: Cyber Security News
Day two of Pwn2Own Berlin 2026 saw hackers unleash devastating attacks on enterprise software and AI tools, adding $385,750 in bug bounties to bring the total to $908,750.
Orange Tsai from DEVCORE stole the show with a brutal Microsoft Exchange exploit, chaining three vulnerabilities to achieve remote code execution with SYSTEM privileges. The attack earned $200,000 and highlights Exchange's role as a critical enterprise target.
Security researchers also escalated privileges on Windows 11 through an integer overflow bug — worth $7,500, next to Exchange's $200,000 — and hit multiple AI coding platforms including Cursor IDE and OpenAI Codex. These AI tools are becoming prime targets due to their access to source code and developer workflows.
DEVCORE leads the competition on 40.5 Master of Pwn points and $405,000 in winnings, and the final day promises more zero-day discoveries. Every vendor now has 90 days to ship a fix before ZDI publishes the details.
Updated August 13, 2026: Pwn2Own Berlin closed on May 16 with $1,298,250 paid out for 47 zero-days, and DEVCORE took Master of Pwn on 50.5 points and $505,000.
Source: Cyber Security News
OpenAI disclosed that two employee devices in its corporate environment were infected during the May 11 TanStack supply chain attack, attributed by researchers to TeamPCP. The attackers exploited weaknesses in package publishing to release 84 malicious artifacts across 42 packages, carrying Mini Shai-Hulud — a variant of the Shai-Hulud worm.
Limited credential material was exfiltrated from a subset of internal source code repositories. OpenAI says it has found no evidence that user data, production systems or intellectual property were affected. It rotated all credentials across the impacted repositories and revoked user sessions.
Those repositories also held code-signing certificates for OpenAI's iOS, macOS and Windows products, which have now been rotated and the apps re-signed. Only macOS users need to act: update ChatGPT Desktop, the Codex app, Codex CLI and Atlas by June 12, 2026, or macOS will start blocking the older builds.
The 84 poisoned versions shipped with valid SLSA Build Level 3 provenance, so signed attestations were no defence. For OpenAI the timing was awkward — it was still hardening after a malicious Axios package reached it through a GitHub Actions workflow in late March.
Source: Security Week
OpenAI disclosed that two employee devices in its corporate environment were infected during the May 11 TanStack supply chain attack, attributed by researchers to TeamPCP. The attackers exploited weaknesses in package publishing to release 84 malicious artifacts across 42 packages, carrying Mini Shai-Hulud — a variant of the Shai-Hulud worm.
Limited credential material was exfiltrated from a subset of internal source code repositories. OpenAI says it has found no evidence that user data, production systems or intellectual property were affected. It rotated all credentials across the impacted repositories and revoked user sessions.
Those repositories also held code-signing certificates for OpenAI's iOS, macOS and Windows products, which have now been rotated and the apps re-signed. Only macOS users need to act: update ChatGPT Desktop, the Codex app, Codex CLI and Atlas by June 12, 2026, or macOS will start blocking the older builds.
The 84 poisoned versions shipped with valid SLSA Build Level 3 provenance, so signed attestations were no defence. For OpenAI the timing was awkward — it was still hardening after a malicious Axios package reached it through a GitHub Actions workflow in late March.
Source: Security Week
A threat actor Cisco Talos tracks as UAT-8616 is exploiting a critical authentication bypass (CVE-2026-20182, CVSS 10.0) in Cisco Catalyst SD-WAN Controller and SD-WAN Manager — formerly vSmart and vManage. Talos says exploitation has been limited so far and clusters it under UAT-8616 with high confidence. Unauthenticated attackers gain administrative access and NETCONF control over network configuration.
CISA added it to the KEV catalog the day it was disclosed and gave federal agencies until May 17 under Emergency Directive 26-03. Fixed releases are 20.9.9.1, 20.12.5.4, 20.12.6.2, 20.12.7.1, 20.15.4.4, 20.15.5.2, 20.18.2.2 and 26.1.1.1 — check which train you're on, since older releases need migrating rather than updating. There's no workaround.
It's at least the fifth Cisco SD-WAN flaw under active exploitation this year. UAT-8616 has been exploiting a nearly identical bypass, CVE-2026-20127, since at least 2023 — Cisco called that exploitation limited, Talos called it extensive. Ten further clusters, distinct from UAT-8616, have been hitting three more SD-WAN bypasses since March, dropping webshells, cryptominers and infostealers.
UAT-8616 targets critical infrastructure and other high-value organizations globally, and reaches root by an unusual route: downgrade the software, exploit the old CVE-2022-20775, then restore the original version. Talos notes the group's infrastructure overlaps with Operational Relay Box networks it monitors. Check auth.log for "Accepted publickey for vmanage-admin" from unfamiliar IPs.
Updated August 13, 2026: Cisco patched another actively exploited SD-WAN Manager flaw in June — CVE-2026-20262, an arbitrary file write rated 6.5, KEV-listed with a June 29 federal deadline. Its fixed releases supersede the May builds: 20.9.9.2, 20.12.7.2, 20.15.4.5, 20.15.5.3, 20.18.3.1 and 26.1.1.2. By then it was the eighth exploited Cisco SD-WAN flaw of 2026.
Source: Dark Reading
A threat actor Cisco Talos tracks as UAT-8616 is exploiting a critical authentication bypass (CVE-2026-20182, CVSS 10.0) in Cisco Catalyst SD-WAN Controller and SD-WAN Manager — formerly vSmart and vManage. Talos says exploitation has been limited so far and clusters it under UAT-8616 with high confidence. Unauthenticated attackers gain administrative access and NETCONF control over network configuration.
CISA added it to the KEV catalog the day it was disclosed and gave federal agencies until May 17 under Emergency Directive 26-03. Fixed releases are 20.9.9.1, 20.12.5.4, 20.12.6.2, 20.12.7.1, 20.15.4.4, 20.15.5.2, 20.18.2.2 and 26.1.1.1 — check which train you're on, since older releases need migrating rather than updating. There's no workaround.
It's at least the fifth Cisco SD-WAN flaw under active exploitation this year. UAT-8616 has been exploiting a nearly identical bypass, CVE-2026-20127, since at least 2023 — Cisco called that exploitation limited, Talos called it extensive. Ten further clusters, distinct from UAT-8616, have been hitting three more SD-WAN bypasses since March, dropping webshells, cryptominers and infostealers.
UAT-8616 targets critical infrastructure and other high-value organizations globally, and reaches root by an unusual route: downgrade the software, exploit the old CVE-2022-20775, then restore the original version. Talos notes the group's infrastructure overlaps with Operational Relay Box networks it monitors. Check auth.log for "Accepted publickey for vmanage-admin" from unfamiliar IPs.
Updated August 13, 2026: Cisco patched another actively exploited SD-WAN Manager flaw in June — CVE-2026-20262, an arbitrary file write rated 6.5, KEV-listed with a June 29 federal deadline. Its fixed releases supersede the May builds: 20.9.9.2, 20.12.7.2, 20.15.4.5, 20.15.5.3, 20.18.3.1 and 26.1.1.2. By then it was the eighth exploited Cisco SD-WAN flaw of 2026.
Source: Dark Reading
Electronics giant Foxconn, Apple's primary iPhone assembler, confirmed a cyberattack disrupted its North American factories. The Nitrogen ransomware group claimed responsibility on its leak site, saying it took 8 terabytes across more than 11 million files, including confidential instructions, projects and drawings from Intel, Apple, Google, Dell, and Nvidia.
Foxconn hasn't confirmed ransomware or data theft either way. Its cybersecurity team implemented measures to keep production and delivery running, and it said affected factories were resuming normal production as of May 12 — without specifying when the attack occurred or which systems were compromised. None of the five named companies would comment.
Nitrogen surfaced in 2023 as a loader distributing ALPHV ransomware, built its own encryptor from leaked Conti code in 2024, and steals data before encrypting systems to maximize pressure on victims. Halcyon's Cynthia Kaiser doubts the haul: recent Nitrogen claims have arrived without a working file listing, which points to a group inflating numbers to push ransoms higher.
The Taiwan-based manufacturer operates factories across Mexico, Wisconsin, Ohio, Texas, Virginia, and Indiana.
Source: CyberScoop
Electronics giant Foxconn, Apple's primary iPhone assembler, confirmed a cyberattack disrupted its North American factories. The Nitrogen ransomware group claimed responsibility on its leak site, saying it took 8 terabytes across more than 11 million files, including confidential instructions, projects and drawings from Intel, Apple, Google, Dell, and Nvidia.
Foxconn hasn't confirmed ransomware or data theft either way. Its cybersecurity team implemented measures to keep production and delivery running, and it said affected factories were resuming normal production as of May 12 — without specifying when the attack occurred or which systems were compromised. None of the five named companies would comment.
Nitrogen surfaced in 2023 as a loader distributing ALPHV ransomware, built its own encryptor from leaked Conti code in 2024, and steals data before encrypting systems to maximize pressure on victims. Halcyon's Cynthia Kaiser doubts the haul: recent Nitrogen claims have arrived without a working file listing, which points to a group inflating numbers to push ransoms higher.
The Taiwan-based manufacturer operates factories across Mexico, Wisconsin, Ohio, Texas, Virginia, and Indiana.
Source: CyberScoop
