GitHub · 2026-05-20 · major
GitHub Internal Repositories Breached via Poisoned VS Code Extension — TeamPCP Claims ~4,000 Repos While GitHub Says Customer Data Untouched
GitHub confirmed an employee device was compromised through a poisoned VS Code extension, exfiltrating internal source-code repositories. TeamPCP is offering roughly 4,000 repos for sale at $50,000.
A malicious VS Code extension on one GitHub employee's machine became the entry point for an internal-repo dump.
What is it?
GitHub disclosed on May 20 that it detected unauthorized access to its internal repositories the day before. The intrusion has been claimed by financially-motivated threat group TeamPCP, which is now offering roughly 4,000 private repos on the Breached forum for a minimum of $50,000.
How does it work?
An employee installed a poisoned VS Code extension from the marketplace. The extension ran code on the developer's machine, harvested credentials, and pivoted into GitHub's internal source-code repositories. GitHub's incident team removed the extension version, isolated the endpoint, rotated critical credentials, and is monitoring for follow-on activity. TeamPCP has previously hit Trivy, Checkmarx, and LiteLLM with similar developer-tooling attacks.
Why does it matter?
Even GitHub — the company whose business is hosting code — was bitten by an IDE-extension supply-chain attack. The takeaway for every AI/coding-agent team: IDE plugins now sit on the same threat surface as npm and PyPI packages, and any AI extension that runs arbitrary code is a credible footprint.
Who is it for?
Security, platform, and engineering teams using VS Code or VS-Code-based forks
Try it
Audit installed VS Code extensions and rotate any tokens accessible to your IDE.