GitHub has confirmed that roughly 3,800 of its internal repositories were exfiltrated after a staff member installed a malicious Visual Studio Code extension. The threat actor group TeamPCP took credit, listing GitHub's source code and internal organisations for sale on a cybercrime forum. GitHub says it detected and contained the breach, and its current assessment is that customer data held outside GitHub's own internal systems was not affected. But the "internal only" framing is doing a lot of work there — those repos contain proprietary code, internal tooling, and potentially secrets that could feed future attacks.

The vector is worth dwelling on. This wasn't a zero-day in GitHub's infrastructure. It wasn't a nation-state exploit chain. It was a developer installing a tool from a marketplace. VS Code extensions are downloaded millions of times a day by the people who build and secure the software the rest of us depend on. The extension marketplace is enormous, poorly audited, and full of packages that request sweeping filesystem and network permissions. Attackers have clearly noticed.

What makes this particularly uncomfortable is the timing. The Grafana breach — covered here Monday — was also rooted in a supply chain failure: a GitHub workflow token left un-rotated after the TanStack npm attack. Two major developer platform incidents in the same week, both tracing back to tooling and token hygiene rather than novel exploitation. The pattern is the message.

For defenders, the immediate lessons are uncomfortable but clear. Developer machines are high-value targets and are often treated as trusted by default on corporate networks. The same person who writes the code that goes into production also has access to build pipelines, secrets managers, and internal repositories. If that workstation is compromised — through a bad extension, a poisoned npm package, or a phishing lure — the blast radius is enormous.

What to watch: GitHub hasn't disclosed which extension was involved or how long it was active before detection. That gap matters — if the extension was published to the marketplace and is still available, other organisations are at risk right now. TeamPCP's track record suggests they're motivated by financial gain, so watch for the stolen repository contents to surface on breach forums or be used as leverage in extortion attempts.

The broader implication is one for the whole industry. Every major software company relies on third-party developer tooling, and very few have mature controls over what their engineers can install on development machines. The VS Code extension attack surface has been a known risk for years — discussed in security research, flagged in red team reports, and largely unaddressed at scale. GitHub just became the case study that makes it impossible to ignore.

Australian software teams using GitHub Enterprise should treat this as a prompt to audit extension policies on developer endpoints. The ACSC's guidance on software supply chain security is directly applicable here — and third-party risk under Australia's SOCI Act extends to development platform dependencies, not just production infrastructure.