GitHub Confirms 3,800 Internal Repos Breached via Trojanized VS Code Extension
GitHub confirms 3,800 internal repositories accessed after employee installs trojanized VS Code extension; TeamPCP seeks $50k for stolen code.

TL;DR
GitHub confirmed that about 3,800 of its internal repositories were accessed after an employee installed a poisoned VS Code extension. The company removed the extension, isolated the device, and began incident response. TeamPCP says it seeks a single buyer for the stolen code or will leak it for free if no offer meets its $50,000 minimum.
Context VS Code extensions are add-ons downloaded from the official marketplace to enhance the editor. In this case, a trojanized version was uploaded and installed by a GitHub employee, granting the attacker access to the employee’s development environment. The extension behaved like a legitimate tool while silently exfiltrating source code from internal repositories.
Key Facts GitHub detected the compromise, removed the malicious extension, isolated the endpoint, and launched an investigation. The company states the activity involved only internal repositories and that there is no evidence customer data outside those repos was affected. TeamPCP, a hacker group previously linked to supply‑chain attacks on PyPI, NPM, Docker, and GitHub, posted on a breach forum claiming possession of ~4,000 private repositories and demanding at least $50,000 for a single buyer, threatening to leak the data for free otherwise.
What It Means The incident shows how a single compromised developer workstation can expose large volumes of proprietary code when extension vetting fails. It underscores the risk of trusted developer tools being weaponized and highlights the need for tighter controls on third‑party plugins.
What Defenders Should Do Enforce an allow‑list for VS Code extensions and require code‑signed packages from verified publishers. Monitor endpoint logs for unusual outbound connections to known malicious domains associated with trojanized extensions. Deploy multi‑factor authentication on all developer accounts and enforce least‑privilege access to internal repositories. Regularly audit installed extensions against GitHub’s security advisories and subscribe to the VS Code Marketplace security feed for rapid removal notices. Finally, test detection rules for MITRE ATT&CK technique T1059.007 (JavaScript/JScript) and T1071.001 (Web Protocols) to catch malicious extension behavior.
Watch for any follow‑up leaks from TeamPCP and for GitHub’s public disclosure of additional indicators of compromise as the investigation continues.
Continue reading
More in this thread
Hank's Furniture January 2026 Data Breach Under Investigation
Peter Olaleru
Poynter Law Group Investigates Hank's Furniture January 2026 Data Breach Affecting Texas Customers
Peter Olaleru
Kentucky Man Sentenced to 70 Years for Cyber‑Enabled Sexual Assault Spree
Peter Olaleru
Conversation
Reader notes
Loading comments...