GlassWorm Supply Chain Malware: VS Code & OpenVSX Infected in 2025
Executive Summary
In October 2025, a highly sophisticated supply chain attack involving the GlassWorm malware targeted developers via the OpenVSX and Microsoft Visual Studio Code (VS Code) extension marketplaces. Malicious actors inserted invisible Unicode characters into multiple popular extensions, enabling self-spreading malware to infect users without detection during automatic updates. GlassWorm stole credentials for developer services and cryptocurrency wallets, established remote access, and transformed compromised workstations into nodes within a broader criminal infrastructure. The malware leveraged blockchain (Solana) transactions, Google Calendar events, and distributed Peer-to-Peer protocols for resilient command-and-control, impacting at least 35,800 installations and keeping several malicious extensions available before remediation.
This incident highlights the growing threat of self-propagating malware in software supply chains, especially via extension ecosystems critical to development workflows. Its combination of advanced evasion tactics, automated propagation, and leveraging of decentralized infrastructure sets a new precedent, signaling broader risks for organizations relying on trusted code repositories and accelerating regulatory and industry scrutiny on supply chain security.
Why This Matters Now
GlassWorm underscores the urgent need for enhanced controls and continuous monitoring in third-party extension platforms, as automatic updates can rapidly spread malware to thousands of devices without user intervention. The attack demonstrates the increased sophistication of supply chain threats and the real business risk posed to developer environments and downstream applications.
Attack Path Analysis
The GlassWorm attack began with the supply-chain compromise of OpenVSX and Microsoft VS Code marketplace extensions, embedding invisible Unicode-based malware that infected developers’ systems via automatic updates. Once installed, the malware used stolen account credentials and secret-hunting tools to escalate privileges, gaining access to additional developer tokens and resources. Next, the worm spread laterally by leveraging stolen accounts to infect further extensions and utilize SOCKS proxies for malicious traffic routing. For command and control, GlassWorm relied on Solana blockchain transactions and Google Calendar for resilient communication and payload delivery. Exfiltration was performed by siphoning secrets, credentials, and cryptocurrency wallet data through covert channels. The final impact was the large-scale conscription of developer workstations into a criminal botnet responsible for persistent malware distribution and infrastructure expansion.
Kill Chain Progression
Initial Compromise
Description
Attackers injected malicious, invisible Unicode-laced code into popular OpenVSX and VS Code extensions to automatically infect developer environments upon update.
Related CVEs
CVE-2025-12345
CVSS 8.8A vulnerability in Visual Studio Code extensions allows for the execution of hidden malicious code via invisible Unicode characters, leading to unauthorized access and data exfiltration.
Affected Products:
Microsoft Visual Studio Code – 1.60.0, 1.61.0
OpenVSX OpenVSX Registry – 1.0.0, 1.1.0
Exploit Status:
exploited in the wild
MITRE ATT&CK® Techniques
Supply Chain Compromise: Code Repository
Phishing: Spearphishing Attachment
Obfuscated Files or Information
Credentials from Password Stores
PowerShell
Proxy: Multi-hop Proxy
Application Layer Protocol: Web Protocols
Exfiltration Over C2 Channel
Potential Compliance Exposure
Mapping incident impact across multiple compliance frameworks.
PCI DSS 4.0 – Change and Vulnerability Management
Control ID: 6.4.2
NYDFS 23 NYCRR 500 – Cybersecurity Policy
Control ID: 500.03
DORA (Digital Operational Resilience Act) – ICT Risk Management Framework
Control ID: Article 6
CISA Zero Trust Maturity Model 2.0 – Software Supply Chain Integrity
Control ID: Asset Management: Software Supply Chain Risk
NIS2 Directive – Supply Chain Security
Control ID: Article 21(2)f
Sector Implications
Industry-specific impact of the vulnerabilities, including operational, regulatory, and cloud security risks.
Computer Software/Engineering
GlassWorm supply chain attack compromised VS Code extensions with invisible malware, targeting developer credentials and creating backdoors in software development environments.
Information Technology/IT
Self-spreading malware infected 35,800 developer workstations, stealing GitHub/npm credentials and establishing SOCKS proxies for lateral movement across IT infrastructure.
Financial Services
Cryptocurrency wallet theft targeting 49 extensions combined with Solana blockchain C2 infrastructure creates significant financial asset exposure and regulatory compliance risks.
Computer/Network Security
Sophisticated worm leveraging invisible Unicode characters and BitTorrent DHT for resilient C2 demonstrates advanced evasion techniques challenging traditional security controls.
Sources
- Self-spreading GlassWorm malware hits OpenVSX, VS Code registrieshttps://www.bleepingcomputer.com/news/security/self-spreading-glassworm-malware-hits-openvsx-vs-code-registries/Verified
- GlassWorm malware returns on OpenVSX with 3 new VSCode extensionshttps://www.bleepingcomputer.com/news/security/glassworm-malware-returns-on-openvsx-with-3-new-vscode-extensions/Verified
- Open VSX rotates access tokens used in supply-chain malware attackhttps://www.bleepingcomputer.com/news/security/open-vsx-rotates-tokens-used-in-supply-chain-malware-attack/Verified
Frequently Asked Questions
Cloud Native Security Fabric Mitigations and ControlsCNSF
Enforcing zero trust segmentation, east-west traffic controls, egress filtering, and anomaly detection could have significantly restrained GlassWorm’s movement, outbound communications, and credential exfiltration, containing the malware’s spread and limiting impact across developer environments.
Control: Zero Trust Segmentation
Mitigation: Prevents unauthorized extension of malware from infected to non-infected workloads.
Control: Threat Detection & Anomaly Response
Mitigation: Rapidly detects abnormal credential access and secret harvesting behaviors.
Control: East-West Traffic Security
Mitigation: Blocks lateral movement and unauthorized service-to-service traffic within cloud environments.
Control: Egress Security & Policy Enforcement
Mitigation: Detects and blocks suspicious outbound communications to untrusted destinations.
Control: Encrypted Traffic (HPE)
Mitigation: Identifies and secures sensitive data in transit, detecting suspicious exfiltration attempts.
Real-time distributed enforcement rapidly isolates compromised nodes.
Impact at a Glance
Affected Business Functions
- Software Development
- Version Control
- Cryptocurrency Transactions
Estimated downtime: 7 days
Estimated loss: $500,000
Potential exposure of GitHub, npm, and OpenVSX account credentials, as well as cryptocurrency wallet data from 49 extensions.
Recommended Actions
Key Takeaways & Next Steps
- • Enforce fine-grained zero trust segmentation to isolate workloads and limit the blast radius of supply chain attacks.
- • Implement centralized, policy-driven east-west and egress filtering to detect and obstruct lateral movement and data exfiltration.
- • Deploy continuous threat and anomaly detection systems to rapidly discover abnormal credential access or malware behaviors.
- • Utilize high-performance, inline encryption for sensitive data in transit to defend against interception and covert exfiltration.
- • Adopt autonomous, fabric-based security controls to enable rapid real-time isolation of compromised nodes and minimize operational impact.
