GitHub has confirmed that attackers linked to the TeamPCP hacking group gained unauthorized access to roughly 3,800 internal repositories after compromising an employee’s machine through a malicious Visual Studio Code extension. The company says the attack appears limited to GitHub’s internal repositories, with no evidence so far that customer repositories, enterprise environments, or public GitHub projects were affected.
TeamPCP allegedly attempted to auction the stolen data on a cybercrime forum, claiming the repositories contained source code and internal organizational information.
Targeting developer tooling rather than production infrastructure directly has become a growing trend in software supply chain attacks. According to GitHub, the company isolated the compromised endpoint, rotated critical credentials, and launched an ongoing investigation after TeamPCP advertised the data for sale for at least $50,000.
Why It Matters: This breach shows how developer environments have become one of the most critical attack surfaces in modern software security. VS Code extensions, npm packages, CI/CD pipelines, and developer credentials increasingly provide attackers with broad access to source code, secrets, cloud infrastructure, and software distribution systems. The GitHub incident also reflects how supply chain compromises can quickly cascade across ecosystems used by millions of developers worldwide.
- VS Code Extension: GitHub stated that the intrusion began after an employee installed a malicious Visual Studio Code extension. Security researchers note that VS Code extensions can access sensitive local resources including SSH keys, cloud credentials, authentication tokens, and repository secrets, making them highly attractive targets for attackers.
- 3,800 Repositories: TeamPCP initially claimed access to around 4,000 GitHub repositories, while GitHub later confirmed that the attackers’ numbers were “directionally consistent” with its own investigation. The stolen data allegedly includes internal source code and organizational information rather than customer repositories.
- No Customer Evidence: The company emphasized that its current investigation has not uncovered signs that external customer repositories, enterprise environments, or user account data were compromised. GitHub also stated it would notify affected customers directly if evidence of broader exposure emerges.
- Broader Attack Wave: Researchers tied TeamPCP to multiple recent attacks involving open-source ecosystems, including compromises affecting Trivy, npm packages, Bitwarden CLI tooling, and Python packages. The same reporting also connects the group to malware campaigns designed to steal credentials, cloud secrets, SSH keys, password vaults, and CI/CD tokens.
- Developer Tooling Risks: Security researchers argue that many organizations lack visibility into which extensions, packages, and developer tools are installed across employee workstations. Because modern development environments often contain privileged credentials and infrastructure access, a single compromised machine can create large-scale downstream exposure.
GitHub Confirms Hack Impacting 3,800 Internal Repositories – Security Week
Attack on GitHub: Data from 3800 internal repositories stolen – Heise
Trusted insights for technology leaders
Our readers are CIOs, CTOs, and senior IT executives who rely on The National CIO Review for smart, curated takes on the trends shaping the enterprise, from GenAI to cybersecurity and beyond.
Subscribe to our 4x a week newsletter to keep up with the insights that matter.
