Ticker feed
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
A security researcher released two Windows zero-day exploits on GitHub on May 13, after a dispute with Microsoft over its handling of their earlier reports. The more serious, "YellowKey", uses a crafted folder on a USB stick or the EFI partition to bypass BitLocker on Windows 11 and Server 2022/2025 in minutes — with physical access.
The public exploit only works against TPM-only BitLocker, which auto-unlocks at boot; it fails against TPM+PIN. The researcher says he has a version that defeats PIN setups too and is withholding it. Windows 10 is unaffected — its recovery architecture differs.
The second exploit, "GreenPlasma", targets the CTFMON service, but the released code is deliberately incomplete — it triggers a UAC prompt by default and lacks the piece needed for a SYSTEM shell. The researcher left that to whoever wants it.
Microsoft says it's investigating and hasn't patched either. A BitLocker PIN plus a BIOS password, per Kevin Beaumont, is the practical mitigation. Treat it as urgent: this researcher's April drops, RedSun and UnDefend, were weaponized in real attacks within days, per Huntress.
Updated August 13, 2026: Microsoft patched YellowKey and GreenPlasma on June 9, 2026, in the same Patch Tuesday that fixed the researcher's MiniPlasma flaw.
Source: Cyber Security News
A security researcher released two Windows zero-day exploits on GitHub on May 13, after a dispute with Microsoft over its handling of their earlier reports. The more serious, "YellowKey", uses a crafted folder on a USB stick or the EFI partition to bypass BitLocker on Windows 11 and Server 2022/2025 in minutes — with physical access.
The public exploit only works against TPM-only BitLocker, which auto-unlocks at boot; it fails against TPM+PIN. The researcher says he has a version that defeats PIN setups too and is withholding it. Windows 10 is unaffected — its recovery architecture differs.
The second exploit, "GreenPlasma", targets the CTFMON service, but the released code is deliberately incomplete — it triggers a UAC prompt by default and lacks the piece needed for a SYSTEM shell. The researcher left that to whoever wants it.
Microsoft says it's investigating and hasn't patched either. A BitLocker PIN plus a BIOS password, per Kevin Beaumont, is the practical mitigation. Treat it as urgent: this researcher's April drops, RedSun and UnDefend, were weaponized in real attacks within days, per Huntress.
Updated August 13, 2026: Microsoft patched YellowKey and GreenPlasma on June 9, 2026, in the same Patch Tuesday that fixed the researcher's MiniPlasma flaw.
Source: Cyber Security News
A supply chain campaign called "mini Shai-Hulud" poisoned around 170 open-source packages on May 11 and 12, including TanStack's react-router, which has over 12 million weekly downloads. UiPath, Mistral AI and Guardrails AI packages were hit too, and this is not the first wave — earlier ones reached Trivy, Bitwarden and Checkmarx.
Two-factor authentication never came into it. The attackers poisoned a GitHub Actions cache and lifted an OIDC token out of the runner's memory to mint a valid npm publish token. The malicious releases then carried genuine provenance attestations, so they showed verified badges pointing at an attacker-controlled build.
The malware writes itself into Visual Studio Code and Claude Code config directories, so it outlives uninstalling the package, and it disguises stolen data as anonymous messaging traffic through the Session app.
TanStack tells anyone who installed an affected version to change every connected cloud, server and developer credential. Do it in the right order: Wiz warns that the malware's gh-token-monitor daemon must be removed first, because revoking tokens while it is still running triggers destructive wiping. Then clear out .vscode and .claude, and block git-tanstack.com.
Source: CyberScoop
A supply chain campaign called "mini Shai-Hulud" poisoned around 170 open-source packages on May 11 and 12, including TanStack's react-router, which has over 12 million weekly downloads. UiPath, Mistral AI and Guardrails AI packages were hit too, and this is not the first wave — earlier ones reached Trivy, Bitwarden and Checkmarx.
Two-factor authentication never came into it. The attackers poisoned a GitHub Actions cache and lifted an OIDC token out of the runner's memory to mint a valid npm publish token. The malicious releases then carried genuine provenance attestations, so they showed verified badges pointing at an attacker-controlled build.
The malware writes itself into Visual Studio Code and Claude Code config directories, so it outlives uninstalling the package, and it disguises stolen data as anonymous messaging traffic through the Session app.
TanStack tells anyone who installed an affected version to change every connected cloud, server and developer credential. Do it in the right order: Wiz warns that the malware's gh-token-monitor daemon must be removed first, because revoking tokens while it is still running triggers destructive wiping. Then clear out .vscode and .claude, and block git-tanstack.com.
Source: CyberScoop
Mini Shai-Hulud is back on npm. On May 11, 84 malicious versions of 42 @tanstack/* packages were published between 19:20 and 19:26 UTC (CVE-2026-45321, CVSS 9.6 Critical). It spread from there into packages from Mistral AI, UiPath and OpenSearch, and into PyPI.
Aikido counted 373 malicious package-version entries across 169 npm package names; Socket, tracking 84 TanStack artifacts, said the real figure was likely at least double its own count. The worm steals npm, GitHub, cloud and CI/CD credentials from developer machines and runners, then republishes itself.
The dangerous part is how it published: a pull_request_target misconfiguration, GitHub Actions cache poisoning, then reading the runner's memory to lift the in-memory OIDC token. That produced malicious packages carrying valid SLSA Build Level 3 provenance — the first npm worm known to do it. Provenance verification alone will not catch this.
Researchers attribute the wave to TeamPCP, which Google tracks as UNC6780, on shared code markers and the group's own claim of credit. But the fully weaponized worm went public on GitHub on the evening of May 12, so the toolchain is now available to anyone, and later waves won't attribute so cleanly.
Order matters when cleaning up. Kill the gh-token-monitor persistence service before rotating anything — revoking tokens first triggers a dead-man's switch that wipes the home directory. Then remove the injected hooks in .claude/ and .vscode/, rotate npm, GitHub and cloud credentials, DNS-block *.getsession.org, and audit publishing logs for releases nobody triggered.
Updated August 13, 2026: The worm resurfaced on June 19 with 1,614 exfiltration repositories tied to 21 compromised GitHub accounts — identity compromise rather than a software flaw, so no CVE and nothing for a vulnerability scanner to find. Researchers attribute that wave to TeamPCP with moderate confidence.
Source: Dark Reading
Mini Shai-Hulud is back on npm. On May 11, 84 malicious versions of 42 @tanstack/* packages were published between 19:20 and 19:26 UTC (CVE-2026-45321, CVSS 9.6 Critical). It spread from there into packages from Mistral AI, UiPath and OpenSearch, and into PyPI.
Aikido counted 373 malicious package-version entries across 169 npm package names; Socket, tracking 84 TanStack artifacts, said the real figure was likely at least double its own count. The worm steals npm, GitHub, cloud and CI/CD credentials from developer machines and runners, then republishes itself.
The dangerous part is how it published: a pull_request_target misconfiguration, GitHub Actions cache poisoning, then reading the runner's memory to lift the in-memory OIDC token. That produced malicious packages carrying valid SLSA Build Level 3 provenance — the first npm worm known to do it. Provenance verification alone will not catch this.
Researchers attribute the wave to TeamPCP, which Google tracks as UNC6780, on shared code markers and the group's own claim of credit. But the fully weaponized worm went public on GitHub on the evening of May 12, so the toolchain is now available to anyone, and later waves won't attribute so cleanly.
Order matters when cleaning up. Kill the gh-token-monitor persistence service before rotating anything — revoking tokens first triggers a dead-man's switch that wipes the home directory. Then remove the injected hooks in .claude/ and .vscode/, rotate npm, GitHub and cloud credentials, DNS-block *.getsession.org, and audit publishing logs for releases nobody triggered.
Updated August 13, 2026: The worm resurfaced on June 19 with 1,614 exfiltration repositories tied to 21 compromised GitHub accounts — identity compromise rather than a software flaw, so no CVE and nothing for a vulnerability scanner to find. Researchers attribute that wave to TeamPCP with moderate confidence.
Source: Dark Reading
