GitHub Breached: Poisoned VS Code Extension Exfiltrates 3,800 Internal Repositories
GitHub confirmed on May 20, 2026 that attackers exfiltrated approximately 3,800 of its internal source code repositories after a poisoned Visual Studio Code extension compromised an employee's device. The threat actor, self-identifying as TeamPCP (tracked by Google Threat Intelligence as UNC6780), uploaded a malicious version of the Nx Console extension to the VS Code Marketplace on May 18. The extension, which had been installed 2.2 million times legitimately, was live for only 18 minutes before removal — but one GitHub employee installed it during that window. The attack chain involved credential harvesting and Sigstore forgery, allowing the attackers to clone internal repositories at scale. GitHub stated there is no evidence of impact to customer information or production systems. The breach highlights the growing risk of developer tooling supply chain attacks, where compromise of a single developer workstation can cascade into massive intellectual property theft. Security researchers from Sophos, Aikido, and Corgea have published detailed analyses of the attack vector, emphasizing that developer endpoints are now the primary target in software supply chain compromises. Organizations are advised to audit installed extensions, implement allow-list policies for VS Code extensions, and enforce multi-factor authentication on developer machines.
This is the most significant developer tooling supply chain attack since SolarWinds. The fact that 18 minutes of exposure was enough to compromise GitHub itself demonstrates that current marketplace security controls are fundamentally insufficient for the threat level.
Was any customer data or code exposed in the GitHub breach?
GitHub confirmed that only internal repositories were affected. The company stated there is no evidence of impact to customer information, customer code, or production systems.
How can developers protect themselves from similar supply chain attacks?
Use extension allow-lists, verify publisher identities before installing, enable auto-update controls, monitor installed extensions for unusual permissions, and enforce MFA on developer accounts and machines.