TeamPCP Breach Exposes 3,800 GitHub Repositories, Source Code Offered for Sale

Context GitHub disclosed that a developer installed a poisoned extension for Visual Studio Code, a widely used code editor owned by Microsoft. This extension acted as a foothold for the threat group TeamPCP, which specializes in software supply chain attacks—operations where malicious code is hidden inside legitimate software to spread further. The breach is part of a broader trend where attackers repeatedly poison open‑source tools to extort victims and erode trust in the software development ecosystem.

Key Facts GitHub’s investigation found at least 3,800 repositories affected, all containing the platform’s own code rather than customer data. TeamPCP announced on BreachForums that it is selling GitHub’s source code and internal organization data, offering samples to prove authenticity. In the months preceding the breach, TeamPCP carried out 20 attack waves, injecting malware into more than 500 distinct open‑source tools and over 1,000 individual code versions.

What It Means The incident shows how a single compromised developer tool can cascade into a large‑scale repository leak, highlighting the risk of trusted extensions in development environments. While no customer code was exposed, the leak of GitHub’s internal source could aid attackers in identifying vulnerabilities for future exploits. The sale attempt also signals a growing market for stolen platform intelligence, which may lower the barrier for other threat actors.\n Mitigations Organizations should audit and approve only verified extensions for IDEs, enforce least‑privilege access for developer accounts, and monitor for anomalous commits or unexpected access patterns. Enabling GitHub’s push protection and secret scanning can help detect leaked credentials or tokens. Applying software bill of materials (SBOM) practices and regularly scanning dependencies for known malicious payloads reduces supply chain risk. Defenders can also watch for MITRE ATT&CK technique T1195 (Supply Chain Compromise) and T1078 (Valid Accounts) in logs.

Watch for further disclosures from GitHub about the extent of the breach and any follow‑up actions taken by TeamPCP on underground markets.