GitHub confirms major breach linked to poisoned VS Code extension
Data from thousands of internal repositories stolen
Hackers have stolen data from thousands of GitHub's internal code repositories after compromising an employee's device through a malicious extension for Visual Studio Code.
The Microsoft-owned software development platform said the breach affected roughly 3,800 internal repositories, describing claims made by a hacking group as "directionally consistent" with its own investigation.
GitHub said there was "no evidence" that customer information stored outside its internal systems had been impacted, but warned that inquiries into the incident were continuing.
In a series of posts on X, the company said it had "detected and contained a compromise of an employee device involving a poisoned VS Code extension".
GitHub did not identify the compromised extension.
Visual Studio Code, commonly known as VS Code, is one of the world's most widely used programming editors. Developers rely on extensions to add features ranging from language support and testing tools to cloud integrations and AI assistants.
Such extensions have become an increasingly attractive target for cybercriminals because they operate close to source code, credentials and software build systems.
TeamPCP claims responsibility
Bleeping Computer reported that TeamPCP, a hacking group previously linked to attacks on software development platforms, has claimed responsibility for the breach and was attempting to sell the stolen data on a cybercrime forum.
The group has also claimed involvement in an earlier breach affecting the European Commission, in which more than 90 gigabytes of data were allegedly stolen from cloud systems belonging to the EU's executive arm.
Cybersecurity experts say the GitHub breach reflects a broader trend in which attackers seek access not by breaking directly into hardened corporate systems, but by exploiting trusted developer tools and dependencies.
OpenAI was recently targeted in a separate but similar attack after hackers compromised Tanstack, a platform used by web developers, to distribute malicious updates capable of stealing passwords and authentication tokens.
One concern for GitHub users is whether attackers may eventually gain access to private repositories if internal credentials or secrets were exposed during the intrusion.
Private repositories often contain commercial software code and internal credentials, despite longstanding guidance that sensitive secrets should never be stored in repositories.
GitHub's security practices
The incident comes during mounting scrutiny over GitHub's security practices.
Last month, researchers at Wiz Research disclosed a remote code execution vulnerability affecting both GitHub.com and GitHub Enterprise Server, which they described as "remarkably easy to exploit".
GitHub has additionally faced criticism over a rise in attacks targeting npm packages, including incidents associated with so-called "Shai-Hulud" malware campaigns.
Mitchell Hashimoto, co-founder of software company HashiCorp, recently criticised the platform's reliability, arguing that automated AI systems scraping public code repositories had contributed to growing instability.
Boris Cipot, principal security engineer at Black Duck, said the attack demonstrated how deeply interconnected modern software development had become.
"A single compromise in developer tooling, CI/CD pipelines, or dependencies can cascade across thousands of organisations," he said.
Cipot added that threat groups increasingly target trusted developer workflows because they offer indirect access to a large number of downstream systems.
"Developer workstations and tools are the primary entry point. Attackers no longer need sophisticated zero days. They exploit trust in everyday tools."
GitHub said it had rotated critical secrets following the breach, prioritising the highest-risk credentials first, and was continuing to monitor systems for signs of further malicious activity.