Loading...
Loading...
A wave of coordinated supply-chain attacks — dubbed Mini Shai‑Hulud and tied to groups like TeamPCP/UNC6780 — has infected npm, PyPI, developer tooling and even GitHub via malicious VS Code extensions and compromised maintainer accounts. Hundreds of npm packages and thousands of internal GitHub repos were implicated, with payloads designed to harvest tokens, SSH keys, cloud credentials and CI secrets, persist through workflows, and propagate across developer endpoints and pipelines. The incidents expose systemic weaknesses in package ecosystems, GitHub Actions configurations, and local developer tooling, prompting urgent calls for pinned dependencies, stronger signing and vetting, hardened workflow permissions, secret scanning and reduced trust in editor/agent extensions.
Coordinated supply-chain worm activity is forcing developers and platform operators to reassess dependency trust, CI defaults and secret hygiene. Tech teams must adapt build and release controls to prevent credential theft and long-lived pipeline persistence.
Dossier last updated: 2026-05-20 19:26:58
Sergiu Gatlan / BleepingComputer : GitHub links the breach of 3,800 internal repositories to the TanStack npm supply-chain attack, saying hackers used a malicious Nx Console VS Code extension — GitHub says the hackers who breached 3,800 internal repositories gained access via a malicious version of the Nx Console VS Code extension …
GitHub disclosed that a developer’s VSCode extension was ‘poisoned’ in a supply-chain attack by a prolific hacker group called TeamPCP, which claims to have accessed roughly 4,000 GitHub repositories and advertised the company’s source code for sale. Security firms say TeamPCP has run at least 20 attack “waves” in recent months, tainting over 500 distinct open-source projects and compromising hundreds of downstream organizations, including AI company Anthropic and data firm Mercor. The group’s playbook inserts malware into widely used developer tools to harvest credentials, push malicious package versions, and then scale further—creating a self-reinforcing cycle of supply-chain compromise. The spree underscores growing systemic risk to software development ecosystems and the need for stronger supply-chain defenses.
GitHub confirmed that about 3,800 internal repositories were breached after an employee installed a trojanized VS Code extension; the malicious extension was removed and the compromised endpoint isolated during ongoing incident response. GitHub says the activity appears limited to internal repositories and there’s no current evidence of exposed customer data outside those repos. The cybercrime group TeamPCP claimed responsibility and is offering the purportedly stolen code for sale, and has been linked to prior supply-chain attacks targeting developer platforms. The incident highlights persistent risks from malicious editor extensions and supply-chain vectors that can expose sensitive corporate source code and developer credentials.
Staged publishing for npm packages
GitHub confirmed a breach via a malicious VS Code extension that compromised an employee device and exfiltrated internal repositories — roughly consistent with the attacker’s claim of ~3,800 repos. The incident highlights a wider, ongoing supply-chain campaign by groups like TeamPCP/UNC6780 that has targeted developer tooling (Trivy, Checkmarx, LiteLLM, Bitwarden CLI, PyTorch Lightning) and npm accounts, pushing malicious packages that harvest tokens, keys, and secrets. The article warns that developer endpoints — laptops running trusted third-party binaries, extensions, and local AI agents — are high‑privilege, under-monitored perimeters; compromising their supply chain bypasses platform controls and can pivot into cloud and production environments. The piece calls for reassessing trust models around local developer tooling and tighter controls on agent/extension distribution and credentials.
GitHub confirmed that roughly 3,800 internal repositories were breached after an employee installed a trojanized Visual Studio Code extension. The company removed the malicious extension from the VS Code Marketplace, isolated the compromised endpoint, and began incident response; it says the activity appears limited to GitHub-internal repositories and has found no evidence of customer data exposure so far. The TeamPCP hacker group claimed responsibility on a cybercrime forum, offering the stolen data for at least $50,000; TeamPCP has been linked to previous supply-chain attacks affecting developer platforms. The incident highlights risks from malicious editor extensions and the wider supply-chain threat to developer tools and code hosts.
&#32; submitted by &#32; <a href="https://www.reddit.com/user/creasta29"> /u/creasta29 </a> <br/> <span><a href="https://neciudan.dev/github-actions-poisoning">[link]</a></span> &#32; <span><a href="https://www.reddit.com/r/programming/comments/1tivw33/httpsneciudandevgithubactionspoisoning/">[comments]</a></span>
GitHub says about 3,800 internal repositories were breached after an employee installed a trojanized VS Code extension; the malicious plugin has been removed and the compromised device isolated. The company believes exfiltration was limited to internal repositories and sees no evidence so far of broader customer data exposure. The TeamPCP hacker group has claimed responsibility and is trying to sell roughly 4,000 repos, citing past supply-chain campaigns that hit developer platforms including PyPI, npm and Docker. The incident underscores risks from malicious IDE extensions and supply-chain attacks across developer tooling, especially given GitHub's central role for millions of developers and organizations.
GitHub confirmed on May 20 that a malicious VS Code extension on an employee device allowed attackers to exfiltrate roughly 3,800 internal repositories, a claim echoed by threat group TeamPCP (tracked by Google as UNC6780) who is offering the code for sale. The incident is part of a broader Mini Shai-Hulud supply-chain campaign traced by Trend Micro, StepSecurity and Snyk that has hit multiple open-source tools and packages (npm, PyPI, Trivy, TanStack, Mistral AI). GitHub isolated the endpoint, removed the extension, and rotated high-impact secrets; the breach exposes infrastructure configuration, deployment scripts and API schemas rather than customer data. Security firms warn this wave highlights rapid exploitation of supply-chain and developer-tooling vectors, increasing risk to software supply chains and AI middleware.
Sergiu Gatlan / BleepingComputer : GitHub confirms breach of ~3,800 repositories after one of its employees installed a malicious VS Code extension; TeamPCP claimed responsibility for the hack — GitHub has confirmed that roughly 3,800 internal repositories were breached after one of its employees installed a malicious VS Code extension.
GitHub confirmed an unauthorized access incident after an employee device was compromised by a malicious Visual Studio Code extension, leading to the exposure of roughly 3,800 internal repositories. The company detected and contained the incident, removed the poisoned extension, isolated affected endpoints, and began an investigation. GitHub said it rotated critical keys overnight, prioritized high-impact credentials, is validating logs and key rotations, and continues monitoring for follow-on activity. The breach appears limited to internal repositories so far; GitHub plans to take further actions as needed and will publish a fuller post-incident report once the investigation concludes. This matters for developer security and supply-chain trust in editor extensions.
Microsoft warned internally that GitHub faces an existential risk as AI coding tools from competitors—Cursor, Anthropic’s Claude Code, and OpenAI-related offerings—change how developers write, debug and collaborate, potentially reducing the need to continuously host code on GitHub. The Information reports Microsoft teams had been trialing multiple tools; a senior exec ordered consolidation onto GitHub Copilot CLI by end of June to standardize toolchains, align with repos and security workflows, and cut costs ahead of FY2027. Microsoft still preserves access to Anthropic models in some Copilot and Microsoft 365 features, and OpenAI has explored building an alternative platform, underscoring pressure on GitHub’s core hosting and service role.
Security researchers have identified a large npm supply-chain attack impacting 314 packages, with dozens flagged as malicious across popular libraries and plugins. Reports list compromised versions of Strapi plugins, litellm, telnyx, and others marked as high risk; some widely used packages (rails, vue) were scanned and deemed safe. The incident matters because compromised npm packages can execute malicious code in developer machines and CI/CD pipelines, spreading to production systems and AI tooling. Developers and security teams should immediately audit dependencies, lock or pin versions, review recent installs, and use supply-chain scanning tools to block or remove infected packages. Vendor advisories and further forensic details are expected as investigations continue.
Bill Toulas / BleepingComputer : Threat actors published 600+ malicious versions to npm as part of the Shai-Hulud supply chain campaign; most of the affected packages are in the @antv ecosystem — Threat actors earlier today published more than 600 malicious packages to the Node Package Manager (npm) index as part of a new Shai-Hulud supply-chain campaign.
&#32; submitted by &#32; <a href="https://www.reddit.com/user/PM-ME-UR-DARKNESS"> /u/PM-ME-UR-DARKNESS </a> <br/> <span><a href="https://krebsonsecurity.com/2026/05/cisa-admin-leaked-aws-govcloud-keys-on-github/">[link]</a></span> &#32; <span><a href="https://www.reddit.com/r/programming/comments/1thze09/cisa_accidentally_leaked_their_own_keys_on_github/">[comments]</a></span>
Security researcher Brian Krebs reports that a public GitHub repository named “Private-CISA” contained plaintext passwords, SSH private keys, tokens and other sensitive CISA assets exposed since at least November 2025. The repo was flagged by GitGuardian and its founder Guillaume Valadon, who says the repository owner did not respond and commit logs indicate GitHub’s default secret-scanning protections had been disabled. The leak points to severe operational security failures at the Cybersecurity and Infrastructure Security Agency (CISA), risking credential theft, system compromise and erosion of trust in a U.S. federal cybersecurity agency. The exposure underscores the need for stronger secret management, automated detection and strict governance for critical infrastructure teams.
Hackers have compromised dozens of popular open source packages in an ongoing supply chain attack
The U.S. Cybersecurity and Infrastructure Security Agency (CISA) mistakenly published sensitive cryptographic keys and digital credentials in a public GitHub repository, exposing internal assets. Security researchers and commenters flagged the leak as severe, noting exposed keys can enable impersonation, code signing abuse, and lateral network access. CISA removed the files after the exposure was reported, but the incident underscores operational security lapses at a high-profile federal cybersecurity agency and raises concerns about credential management, secrets scanning, and supply-chain risk. The episode matters because it weakens trust in a national cyber-defender, may require credential revocation and audits, and highlights the need for stricter developer workflows and automated secret-detection tooling across government and industry.
Security researchers at SafeDep disclosed on May 19, 2026 that the npm account atool was breached and used to publish 637 malicious releases across 317 packages in a 22-minute burst. The payload is a 498KB obfuscated Bun script matching the Mini Shai-Hulud toolkit seen in a recent SAP supply-chain attack; it harvests an extensive range of credentials (AWS, GitHub PATs, npm tokens, Kubernetes service accounts, Vault, SSH keys, etc.), attempts container escape, and exfiltrates data by committing Git objects to public GitHub repos. The malware achieves persistence via systemd/LaunchAgent, GitHub Actions workflow injection, VS Code tasks, and AI-agent hooks (Claude Code, Codex), abuses OIDC to mint npm publish tokens, and even signs artifacts through Sigstore using stolen identities. The scale, automated propagation via preinstall hooks and optionalDependencies, and the ability to forge provenance make this a major supply-chain and CI/CD threat to the JavaScript ecosystem.
A maintainer account for the npm scope atool was compromised and an attacker published 631 malicious releases across 314 packages in about 22 minutes, including popular modules like @antv, echarts-for-react, size-sensor and timeago.js. The injected code aims to exfiltrate credentials and secrets—AWS keys, GitHub tokens, npm credentials, SSH keys, DB strings, Docker/Kubernetes tokens—and can escape containers if the Docker socket is exposed to gain privileged host access. This supply-chain incident underscores the risks of compromised maintainer accounts and the need for strict package signing, multi-factor authentication, secret scanning, container hardening, and rapid incident response to protect downstream projects and production systems.