GitHub Internal Repositories Breached via Malicious Nx Console VS Code Extension

GitHub on Wednesday officially confirmed that the breach of its internal repositories was the result of a compromise of an employee device involving a poisoned version of the Nx Console Microsoft Visual Studio Code (VS Code) extension. The development comes as the Nx team revealed that the extension, nrwl.angular-console, was breached after one of its developers' systems was hacked in the wake of the recent TanStack supply chain attack, which has also impacted OpenAI, Mistral AI, and Grafana Labs.

"We have no evidence of impact to customer information stored outside of GitHub's internal repositories, such as our customer's own enterprises, organizations, and repositories," Alexis Wales, Chief Information Security Officer of GitHub, said in a statement. "Some of GitHub's internal repositories contain information from customers, for example, excerpts of support interactions. If any impact is discovered, we will notify customers via established incident response and notification channels."

The attack is said to have allowed the threat actor, a cybercriminal group known as TeamPCP, to exfiltrate about 3,800 repositories. GitHub said it has taken steps to contain the incident and rotated critical secrets, adding it's continuing to monitor the situation for follow-on activity.

"This incident highlights that there need to be deeper, more fundamental changes to how we and other maintainers need to think about securing developer tooling and open source distribution," said Jeff Cross, co-founder of Narwhal Technologies, the company behind nx.dev. "We're also beginning conversations with other high-profile open source maintainers about how we can work together on some of the deeper structural problems around software supply chain security. A lot of the assumptions the ecosystem has operated under for years no longer hold."

In recent months, TeamPCP has rapidly gained notoriety for large-scale software supply chain attacks, specifically going after widely-used open-source projects and security-adjacent tools that developers rely on.

What's notable here is that the trojanized version of the VS Code extension was live on Visual Studio Marketplace only for eighteen minutes (between 12:30 p.m. and 12:48 p.m. UTC on May 18, 2026). But this short window was enough for the attackers to distribute a credential stealer capable of harvesting sensitive data from 1Password vaults, Anthropic Claude Code configurations, npm, GitHub, and Amazon Web Services (AWS).

"The extension looked and behaved like normal Nx Console, but on startup it silently ran a single shell command that downloaded and executed a hidden package from a planted commit on the official nrwl/nx GitHub repository," OX Security researcher Nir Zadok explained. "The command was disguised as a routine MCP setup task so it would not raise suspicion."

The interlinked nature of modern software has allowed TeamPCP to unleash a self-sustaining cycle of new compromises. The pattern that drives home this aspect is deceptively simple as it's nefarious: break into one trusted tool, steal credentials from developer systems that may install it, and use those credentials to break into the next legitimate tool.

"Every popular extension marketplace ships with auto-update on by default. VS Code, Cursor, the whole lineup," Aikido security researcher Raphael Silva said. "The reasoning makes sense in isolation, because most developers never update anything manually, so leaving it off means a long tail of editors running stale, vulnerable code."

"The trade-off stops making sense once you account for hostile/compromised publishers. Auto-update gives an attacker who controls a release a direct push channel into every machine running that extension. Marketplaces don't impose any review gate or waiting period between when an update is published and when installed clients pull it in."

Practical Takeaways for Developers

This incident serves as a critical reminder for developers and organizations to implement several security best practices:

1. Verify Extension Sources: Always download extensions from official marketplaces and verify publisher authenticity before installation.

2. Monitor Extension Updates: Be cautious when extensions update unexpectedly, especially if changes aren't documented.

3. Implement Code Signing: For internal tools, consider implementing code signing to ensure only authorized code runs on developer machines.

4. Use Multi-Factor Authentication: Enable MFA across all development platforms to mitigate credential theft risks.

5. Regular Security Audits: Conduct regular security audits of third-party dependencies and tools used in the development workflow.

6. Network Segmentation: Isolate development environments from production systems to limit potential blast radius of such attacks.

7. Supply Chain Security: Implement software supply chain security measures such as SBOMs (Software Bill of Materials) and dependency scanning.

The GitHub breach underscores the evolving sophistication of supply chain attacks and the critical need for enhanced security measures across the entire development ecosystem. As developers increasingly rely on third-party tools and extensions, the attack surface continues to expand, making robust security practices more essential than ever.