GitHub says internal repos exfiltrated after poisoned VS Code extension attack
GitHub has reported that internal repositories were exfiltrated due to a malicious Visual Studio Code extension. The company is currently analyzing logs and monitoring for further activity while assuring that customer data remains safe. Concerns have been raised about the potential risk to private repositories and the implications of the attack on the platform's security.
- ▪GitHub fell victim to a poisoned VS Code extension that led to the exfiltration of internal repositories.
- ▪The attackers, linked to the TeamPCP malware crew, claimed to have access to around 4,000 repositories and threatened to leak the code if not sold.
- ▪There are concerns regarding the security of private repositories and the potential leakage of sensitive commercial code.
4 outlets in our directory ran this story, first to last over 23 hours. All of the coverage we found sits in one bucket: centre. That one-sidedness is itself worth noticing.
- ▪ GitHub ~3,800 internal repos compromised through a malicious VS Code extension — r/netsec
- ▪ GitHub confirms 3,800 internal repos stolen through poisoned VS Code extension as supply chain worm hits Microsoft’s Python SDK — VentureBeat
- ▪ GitHub Confirms 3,800 Internal Repos Stolen Through Poisoned VS Code Extension — Decrypt
The Register publishes from United Kingdom and files mainly under tech. We currently carry 390 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Story provenance
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | theregister |
| Canonical URL | https://www.theregister.com/devops/2026/05/20/github-says-internal-repos-exfiltrated-after-poisoned-vs-code-extension-attack/5243206 |
| Publication time | Wed, 20 May 2026 12:27:44 +0200 |
| Retrieval time | 2026-05-20T11:08:54.398Z |
| Last seen | 2026-05-20T11:08:54.398Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | g3tmfZ61Bsa8 · 4 stories |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Opening excerpt (first ~120 words) tap to expand
(function() { let windowUrl = window.location.href; windowUrl = windowUrl.substring(windowUrl.indexOf('?') + 1); let messageElement = document.querySelector('.shareableMessage'); if (windowUrl && windowUrl.includes('code') && windowUrl.includes('expires')) { messageElement.style.display = 'block'; } })(); DevOps GitHub says internal repos exfiltrated after poisoned VS Code extension attack Initial assessment says customer data spared while users wonder what else may have slipped out Tim Anderson Tim Anderson Published wed 20 May 2026 // 11:27 UTC GitHub, the world's biggest code repository and DevOps platform, fell victim to a malicious Visual Studio Code (VS Code) extension.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at theregister.
Discussion
0 commentsMore from theregister
