GitHub breached through a poisoned VS Code extension
A poisoned Nx Console release was live for minutes on 18 May and still reached GitHub. What an editor extension can reach, and five checks for your keys.
Published · 4 min read

On 18 May 2026 an attacker published a poisoned version of Nx Console, an extension for the VS Code editor, using a contributor's stolen credentials. Nx says it was live on Microsoft's Visual Studio Marketplace for about 11 minutes, and on the Open VSX registry for about 36, before it was pulled. That was long enough to reach GitHub: the same day, GitHub detected and contained a compromise of an employee's device "involving a poisoned VS Code extension published by a third party", in a statement that links to the Nx Console advisory. By its own assessment the attacker took GitHub's internal repositories, about 3,800 of them by the attacker's count, a figure GitHub called "directionally consistent" with its investigation.
GitHub said it had no evidence of impact to customer information stored outside those internal repositories, though some of them hold information from customers, such as excerpts of support interactions. It rotated critical secrets that Monday and into Tuesday, the highest-impact first, and promised a fuller report once its investigation is complete. A group calling itself TeamPCP offered the code for sale on a cybercrime forum for US$50,000, The Record reported.
Four ordinary links in one chain
The Nx team's own account, published on 21 May, is the useful part, because every link in it is ordinary. A week earlier a contributor ran a routine install that pulled in a malicious package from an earlier attack on another project, TanStack, and it took the contributor's GitHub token. The repository being worked on had a setting meant to refuse packages less than a week old, but the pinned version of the install tool silently ignored it. The token sat where any program running as that user could read it. And any core contributor could publish a release without a second person's approval. The upload even passed the Marketplace's automated checks. It was caught because a maintainer received the routine email every upload triggers, and was not expecting a release.
An editor extension runs with the developer's own permissions, so it can reach whatever the developer can. This one went looking for exactly that, Nx says: tokens for GitHub, npm and AWS, Google Cloud and Docker credentials, Vault tokens, SSH keys, .env files and any open 1Password command-line session. Its advice to anyone who installed it is blunt: treat anything reachable from the machine as exposed, and rotate every credential that was on it.
Your code, your accounts, your keys
For an organisation that pays for software, a developer's laptop is part of its security whether it owns the laptop or not. Whether the people building your system are your own staff, an agency or one person like me, their machines hold keys to your repository and your cloud accounts, and an extension update nobody noticed can hand those keys to someone else.
That is why who owns the accounts matters more than who wrote the code. On my builds the repository, the hosting and the data are the client's, and my access to them is the client's to grant and to take away. On a day like 18 May, that is the difference between waiting for a supplier to rotate your secrets and rotating them yourself, provided you know where every key is and who holds one.
Five checks for the machines that hold your keys
- Ask your developers which editor extensions they run, and agree a short approved list. Sophos, whose teams found affected customers of their own, says to look first at extensions from new or rarely seen publishers.
- Keep the repository, the hosting and the cloud accounts in your organisation's name, so you can remove anyone's access in minutes.
- Prefer short-lived tokens with a narrow scope, and single sign-on for source control, to long-lived keys left in files.
- Require a second person to approve anything that ships. A two-person rule for releases is what Nx calls its central fix.
- Write down every secret your system uses and where it lives. If you cannot list them, you cannot rotate them in an afternoon.
If your developers are capable but this kind of hardening is new to them, that is the work behind Guide it, and the fit check is the place to start.
Sources
- GitHub, Investigation update: GitHub Enterprise Server signing key rotation, 20 May 2026
- Nx, Postmortem: Nx Console v18.95.0 supply-chain compromise, 21 May 2026
- Sophos X-Ops, GitHub internal repositories breached.
- The Record, GitHub confirms being hacked by TeamPCP, says customer data unaffected, 20 May 2026
Enrique Lacambra III builds internal business systems from Cainta, Rizal.
Tell me what is broken and I will tell you if it is worth building. A 20-minute call, no charge, and I will say so if you do not need me.
