Key Takeaways
A sophisticated supply-chain attack has compromised 3,800 of GitHub’s internal code repositories, deepening a crisis at the Microsoft-owned developer platform that includes a leadership exodus, persistent service outages, and growing competitive threats. The breach, carried out by the financially motivated hacking group TeamPCP, stemmed from a single employee installing a poisoned extension for Visual Studio Code, Microsoft’s popular code editor.
"We removed the malicious extension version, isolated the endpoint and began incident response immediately," GitHub said in a statement, confirming that critical secrets were rotated. The company’s Chief Security Officer, Alexis Wales, later confirmed the attack vector was a malicious version of the Nx Console extension, v18.95.0, which was live on the official marketplace for just 18 minutes on May 18. Despite the brief window, auto-updates may have pushed the malicious package to over 6,000 users.
The attack, assigned identifier CVE-2026-48027, involved a credential-stealing payload known as SANDCLOCK that was fetched from a hidden package. The initial entry point for the attackers was a prior compromise of open-source developer tool TanStack on May 11, which allowed them to steal the GitHub credentials of an Nx Console developer. TeamPCP initially offered the 3,800 stolen repositories for sale for $50,000, later raising the price to $95,000 after appearing to partner with the Lapsus$ hacking group.
The security breach compounds a period of internal turmoil that began after former CEO Thomas Dohmke’s departure last year. Microsoft opted not to name a successor, instead folding GitHub into its CoreAI team, led by former Meta executive Jay Parikh. The move has been followed by an exodus of senior leaders, including 34-year Microsoft veteran Julia Liuson and Chief Revenue Officer Elizabeth Pemmerl. The instability and frequent service outages have led developers to publicly question the platform's reliability, with some high-profile projects announcing their departure.
The GitHub incident is the most visible consequence of a months-long campaign by TeamPCP (tracked by Google’s Threat Intelligence group as UNC6780) targeting the software development ecosystem. The group’s method is a self-perpetuating cycle: compromise a popular developer tool to steal credentials, then use those credentials to publish malicious versions of other tools, widening their access.
Grafana Labs confirmed it was also compromised via the same initial TanStack attack, receiving a ransom demand on May 16 which it declined to pay. Two employee devices at OpenAI and certain code repositories at Mistral AI were also compromised in the same wave of attacks.
"Developer workstations now possess the same strategic value as domain controllers," Morey Haber, chief security adviser at BeyondTrust Corp., said in an email. "Access to source code repositories, secrets, SSH keys, cloud credentials, signing certificates and deployment pipelines can transform a single compromised endpoint into a cascading supply chain incident."
While GitHub maintains that no customer code was affected, the breach of its own platform code gives attackers insight into its architecture, potentially enabling future zero-day exploits. The incident highlights the strategic challenge facing Microsoft, which acquired GitHub for $7.5 billion in 2018. The platform is not just a product but the foundation of Microsoft's relationship with the developer community.
The crisis comes as GitHub's AI-powered Copilot tool is losing its first-mover advantage to competitors like Cursor and Claude Code. Internal sources report that Jay Parikh has warned colleagues that GitHub faces a "severe threat." The combination of security failures, operational instability, and a perceived loss of direction risks eroding the developer trust that is GitHub's most critical asset, creating an opening for rivals to reshape the market.
This article is for informational purposes only and does not constitute investment advice.
