Trending Now RSS

Visual Studio Code

Saves to local browser storage. Followed topics appear on the homepage and refresh on each visit.
More context

Multiple reports say a malicious VS Code extension was used to compromise and exfiltrate data from about 3,800 internal GitHub repositories. Attackers associated with TeamPCP allegedly targeted developers and attempted to sell stolen source code for $50,000.

Also known as vs code·vscodium·code - oss·vs code extension·vs code insider

0.7 Activity score down · 2d
4.0 Peak score 3d window
Negative Sentiment
4 Sources · 4 signals
Last updated · next ~11:00
3d First on radar
Key Takeaway A poisoned VS Code extension is linked to large-scale compromise and data theft from roughly 3,800 internal GitHub repositories.
AI summary · grounded in cited sources
VS Code supply chain GitHub repo exfiltration Malicious developer plugins vs code vscodium
Negative 12/100
AI Brief

A poisoned VS Code extension is linked to large-scale compromise and data theft from roughly 3,800 internal GitHub repositories.

Multiple reports say a malicious VS Code extension was used to compromise and exfiltrate data from about 3,800 internal GitHub repositories. Attackers associated with TeamPCP allegedly targeted developers and attempted to sell stolen source code for $50,000.

Trending Activity ▼ -2.6 24h
Trend score · left axis Sentiment score · right axis

Live Wire

Top 2 signals · A poisoned VS Code extension is linked to large-scale

Broader Visual Studio Code coverage

Other Visual Studio Code activity — not part of the “A poisoned VS Code extension is linked to large-scale” story

Briefing Findings · A poisoned VS Code extension is linked to large-scale

Story-specific findings extracted from this briefing's coverage. Fast Facts in the sidebar holds the canonical reference data (CEO, founded, ticker).

affected repos about 3,800 internal GitHub repositories
attack vector poisoned/malicious VS Code extension
threat actor claim TeamPCP claimed the source code theft
outcome internal repos exfiltrated after the extension attack

What to Watch

  • Check your VS Code extension inventory for the specific malicious extension name reported in coverage.
  • Follow GitHub security updates and advisories for any official follow-ups tied to this VS Code extension incident. The Register

What Changed

  • GitHub ~3,800 internal repos compromised through a malicious VS Code extension Tom's Hardware
  • Hacker group hits 3,800 internal GitHub repositories via poisoned developer plugin — TeamPCP claims source code theft and attempts $50,000 sale, employee installed malicious VS Code extension Tom's Hardware
  • GitHub says internal repos exfiltrated after poisoned VS Code extension attack The Register
Source-backed brief 2 articles across 2 publications · brief is source backed Show all sources
Broader Visual Studio Code coverage · not part of the A poisoned VS Code extension is linked to large-scale story

Latest from across the web

External coverage we have crawled and indexed for this topic.

View all 5 signals →

What each outlet is saying

Source-by-source view of what publications and communities are surfacing right now.

Discovery

Videos

Topic-matched media from the channels we track
Share & embed Quotables, social share, embed snippet

Share

Quotables · click to copy

Verbatim claims you can cite from the briefing. Each quote is sourced from indexed coverage — paste into your own writing or social.

Embed widget

<script src="https://ttek2.com/embed/pulse/visual-studio-code" async></script>