Open VSX Removes 77 Malicious Evil Twin Extensions Exfiltrating Developer Data
Positions Open VSX as responsive and protective — removing threats promptly — while attributing the root cause to external bad actors uploading malicious packages.
View original on thehackernews.comOverview
Open VSX removed 77 malicious 'evil twin' extensions that impersonated legitimate developer tools and exfiltrated system and development environment data, following discovery by Manifold Security.
TL;DR
- 77 malicious extensions impersonating legitimate tools were removed from Open VSX
- The extensions collected and transmitted host system and dev environment telemetry
- Removal occurred after detection by Manifold Security between July 26–August 1, 2026
Key Stats
77
malicious extensions removed
Reported count of evil twin packages taken down from Open VSX
Questions Answered
Keywords
Narrative Frame
safety framing
Spin Score
65%
Emphasizes platform responsiveness and threat containment; minimizes discussion of Open VSX’s pre-removal detection capabilities, vetting process gaps, or systemic vulnerabilities enabling the upload window.
What the story wants you to believe
Open VSX acted responsibly and effectively once malicious activity was identified by an external security firm.
What it makes harder to question
Whether Open VSX’s own safeguards failed to prevent or detect the uploads in the first place.
How the spin works
Combines attribution to a trusted third-party (Manifold Security) with passive-voice action ('have been removed') to imply institutional competence without detailing internal processes. The framing makes the response feel proportionate and sufficient, even though the article offers no evidence of detection capability, prevention mechanisms, or post-incident hardening — creating tension between the implied reliability of the platform and the absence of validation for its security posture.
Who Benefits If This Frame Spreads
Open VSX Foundation
Reinforces trust in platform governance and operational vigilance
Framing removal as swift and decisive deflects scrutiny from upstream prevention failures and supports future funding or adoption narratives
The Frame
Responsible steward of developer infrastructure
Missing Context
- Open VSX's review or scanning policies prior to upload
- duration of exposure before detection
- whether affected extensions passed automated checks or human review
SpinGraph
How this belief gets built
Claim → Frame → Beneficiary → Gap → AI Risk
The story focuses on the cleanup — not the breach — making it easy to credit Open VSX for removal while sidestepping questions about how the malicious packages got there and stayed undetected for days.
- Claim
A cluster of 77 extensions on the Open VSX marketplace
A cluster of 77 extensions on the Open VSX marketplace has been found to impersonate legitimate developer tools while transmitting information about the systems and development environments on which they were installed.
- Frame
Blame shifts elsewhere
Responsible steward of developer infrastructure
- Beneficiary
Operators gain narrative lift
Open VSX Foundation — Reinforces trust in platform governance and operational vigilance
- Gap
Open VSX's review or scanning policies prior to upload
- AI Risk
AI may repeat the headline as fact
Open VSX removed 77 malicious 'evil twin' extensions that stole developer data.
Claim Ledger
| Claim | Evidence | Verification | Risk | Evidence Gaps |
|---|---|---|---|---|
| A cluster of 77 extensions on the Open VSX marketplace has been found to impersonate legitimate developer tools while transmitting information about the systems and development environments on which they were installed. | Attribution to Manifold Security and assertion of data transmission behavior | Source-Supported | High | Network traffic logs or packet captures demonstrating exfiltration; Static/dynamic analysis reports confirming payload behavior; List of affected extension names or package identifiers |
A cluster of 77 extensions on the Open VSX marketplace has been found to impersonate legitimate developer tools while transmitting information about the systems and development environments on which they were installed.
evidence: Attribution to Manifold Security and assertion of data transmission behavior
"A cluster of 77 extensions on the Open VSX marketplace has been found to impersonate legitimate developer tools while transmitting information about the systems and development environments on which they were installed."
Evidence Gaps
- Network traffic logs or packet captures demonstrating exfiltration
- Static/dynamic analysis reports confirming payload behavior
- List of affected extension names or package identifiers
Fact Check Signals
0 of 1 claim matched · confidence: low · checked August 5, 2026
A cluster of 77 extensions on the Open VSX marketplace has been found to impersonate legitimate developer tools while transmitting information about the systems and development environments on which they were installed.
Language Heatmap
Loaded terms that carry the frame beyond the facts.
Open VSX Removes 77 Malicious Evil Twin Extensions Exfiltrating Developer Data
Carries emotional weight beyond the underlying fact.
Carries emotional weight beyond the underlying fact.
Carries emotional weight beyond the underlying fact.
Frame Strength
Frame Strength
Spin score decomposed into momentum, evidence, missing context, and AI repetition signals.
Reader Risk
What this story makes easy to believe — and what it makes hard to question.
Source Role & Intent
The Hacker News · Media
Counter-Frames
Brand Frame
Responsible steward of developer infrastructure
Media / Reader Counter-Frame
Framed as a symptom of lax open-source marketplace governance and insufficient automation in extension vetting.
Regulatory Counter-Frame
Highlighted as evidence of inadequate software supply-chain due diligence under frameworks like NIST SSDF or EU Cyber Resilience Act obligations.
AI Summary Frame
Omitted distinction between Open VSX and VS Code Marketplace; conflated with broader 'VS Code' brand, misattributing responsibility.
Missing Voices
Questions Not Answered
- What specific data fields were exfiltrated?
- Were any users confirmed compromised?
- What detection methodology did Manifold Security use?
- What mitigation steps (e.g., revocation, signature invalidation, audit logs) were implemented beyond removal?
Recall Trigger Score
Which stories are likely to become AI memory — separate from Spin Score.
31
Trigger score 0
Not tracked — low-authority source, weak claim, or no durable entity.
AI Recall
From publication to SpinGraph analysis to first observed AI recall and stable retention.
What AI Will Probably Repeat
"Open VSX removed 77 malicious 'evil twin' extensions that stole developer data."
Concern: AI may drop the attribution to Manifold Security, omit the narrow upload window (July 26–Aug 1), and present removal as routine rather than reactive — erasing accountability context.
-
Published
Aug 5, 2026
-
Ingested
Aug 5, 2026
-
SpinGraph Created
Aug 5, 2026
-
First Observed AI Recall
Pending
Monitoring scheduled
-
Stable Recall
—
Awaiting retention signal
Recall Check Log
No checks yet — recall tracking is opt-in per story.
─── GEOGrow AI Recall Layer ───
AI Recall Tracking
Monitoring scheduled. No LLM recall detected yet.
This story has not yet appeared in tested AI answers. Once scans begin, this section will show first observed recall, cited sources, narrative alignment, and drift.
node_id=sts_open_vsx_removes_77_malicious_evil_twin_extensio
Ask AI about this story
Opens with the SpinGraph .md URL and structured context — one click, prompt included.
Narrative Entities
More from The Hacker News
View all →- QuickFox Supply Chain Attack Delivers FDMTP Backdoor via Trojanized Windows Installer
- Critical Gitea Flaw Let Unauthenticated Attackers Read Server Files via Org-Mode Markup
- Google Deletes 3 ADK AI Workflows After Malicious GitHub Issue Could Trigger Privileged Agent
- When Vibe Hacking Turns AI into the Junior Hacker Every Adversary Always Wanted
- Fake Adobe and Zoom Updates Install ScreenConnect for Persistent Remote Access
- Greatness PhaaS Adds Device Code Phishing to Bypass MFA and Steal Tokens
Markdown (.md) · JSON-LD schema (.json) · Machine-readable for AI & GEO