Executive Summary
In early 2024, a sophisticated supply chain attack targeting the Visual Studio Code (VS Code) developer ecosystem was uncovered, leveraging a self-propagating worm dubbed 'GlassWorm.' The attack exploited weaknesses in package distribution and dependency validation, spreading rapidly via malicious code hidden in open-source extensions and packages. Once executed on developer machines, GlassWorm covertly harvested credentials and turned compromised systems into nodes for broader criminal infrastructure, affecting nearly 36,000 endpoints globally. The incident illuminated the risks posed by highly automated, invisible code propagation through trusted development tools, impacting developer productivity and increasing the potential for downstream compromise across organizations that rely on shared code repositories.
This breach is emblematic of the accelerating trend of supply chain attacks against development environments, with threat actors increasingly leveraging automation and legitimate software to undermine trust. The GlassWorm incident underscores the urgency for enhanced visibility, stringent code validation, and zero trust controls in modern software supply chains to counter evolving adversary tactics.
Why This Matters Now
The GlassWorm attack on the VS Code supply chain highlights a pressing vulnerability for organizations relying on open-source and third-party tools. The capacity for self-propagation and credential theft in widely adopted developer platforms creates urgent risks—potentially enabling attackers to compromise not just single targets but entire ecosystems through trusted channels.
Attack Path Analysis
The GlassWorm attack began by compromising the VS Code supply chain, delivering malicious updates that infected developer machines. The worm escalated privileges by stealing user credentials and expanding its control. It leveraged lateral movement to silently traverse cloud workloads and developer environments undetected. After establishing persistent command & control channels, the adversary covertly exfiltrated sensitive data and credentials. This widespread exfiltration and conversion of developer endpoints into criminal proxies led to major operational and reputational impact.
Kill Chain Progression
Initial Compromise
Description
Attackers injected malicious code into the VS Code supply chain, distributing compromised extensions or updates that infected nearly 36,000 developer machines.
Related CVEs
CVE-2025-55319
CVSS 8.8A command injection vulnerability in Visual Studio Code allows unauthorized remote code execution via network access.
Affected Products:
Microsoft Visual Studio Code – 1.104.0
Exploit Status:
proof of conceptCVE-2025-32726
CVSS 6.8An improper access control vulnerability in Visual Studio Code allows local privilege escalation.
Affected Products:
Microsoft Visual Studio Code – < 1.99.1
Exploit Status:
no public exploitCVE-2025-62453
CVSS 5A security feature bypass vulnerability in GitHub Copilot and Visual Studio Code allows local attackers to bypass security features.
Affected Products:
Microsoft Visual Studio Code – < 1.105.0
Exploit Status:
no public exploit
MITRE ATT&CK® Techniques
Supply Chain Compromise: Compromise Software Supply Chain
Command and Scripting Interpreter
Valid Accounts
Credentials from Password Stores
Obfuscated Files or Information
Ingress Tool Transfer
Phishing: Spearphishing Attachment
Remote Access Software
Potential Compliance Exposure
Mapping incident impact across multiple compliance frameworks.
PCI DSS 4.0 – Change and Development Processes
Control ID: 6.4.3
NYDFS 23 NYCRR 500 – Application Security
Control ID: 500.08
DORA – ICT Risk Management Framework
Control ID: Article 6
CISA Zero Trust Maturity Model 2.0 – Supply Chain Security Monitoring
Control ID: Asset Management
NIS2 Directive – Security of Supply Chains
Control ID: Article 21(2)(d)
Sector Implications
Industry-specific impact of the vulnerabilities, including operational, regulatory, and cloud security risks.
Computer Software/Engineering
GlassWorm supply chain attacks directly target VS Code development environments, compromising source code integrity and enabling credential theft across software development workflows.
Information Technology/IT
IT infrastructure faces severe risk from self-propagating worms turning systems into criminal proxies, requiring enhanced east-west traffic security and zero trust segmentation.
Financial Services
Financial institutions vulnerable to credential theft and lateral movement attacks through compromised developer tools, threatening sensitive data and regulatory compliance frameworks.
Computer/Network Security
Security firms must address sophisticated supply chain compromises affecting development tools while implementing threat detection and anomaly response capabilities for client protection.
Sources
- Self-Propagating GlassWorm Attacks VS Code Supply Chainhttps://www.darkreading.com/application-security/self-propagating-glassworm-vs-code-supply-chainVerified
- GlassWorm Supply Chain Attack: Self-Spreading Malware Infects Visual Studio Code (VS Code) Extensions via OpenVSX and Microsoft Marketplacehttps://www.rescana.com/post/glassworm-supply-chain-attack-self-spreading-malware-infects-visual-studio-code-vs-code-extensionVerified
- CVE-2025-55319 Impact, Exploitability, and Mitigation Stepshttps://www.wiz.io/vulnerability-database/cve/cve-2025-55319Verified
- GlassWorm Malware Returns: VS Code, npm, Go, Rust Hithttps://byteiota.com/glassworm-malware-returns-vs-code-npm-go-rust-hit/Verified
Frequently Asked Questions
Cloud Native Security Fabric Mitigations and ControlsCNSF
A robust Cloud Network Security Framework with zero trust segmentation, east-west traffic controls, real-time threat detection, and strict egress enforcement would have significantly contained GlassWorm’s ability to escalate, move laterally, establish C2, and exfiltrate data—reducing both spread and business impact.
Control: Threat Detection & Anomaly Response
Mitigation: Suspicious installation or anomalous network traffic from infected endpoints would have triggered alerts.
Control: Zero Trust Segmentation
Mitigation: Identity and workload segmentation prevents excessive privilege access and lateral movement through least privilege policies.
Control: East-West Traffic Security
Mitigation: Microsegmentation isolates workload-to-workload traffic, blocking unauthorized lateral traversal.
Control: Egress Security & Policy Enforcement
Mitigation: Outbound traffic is restricted to approved destinations, blocking connections to unknown C2 endpoints.
Control: Cloud Firewall (ACF)
Mitigation: Cloud firewall policies and threat intelligence block data exfiltration and alert on abnormal transfer patterns.
Autonomous, distributed network security surfaces the attack, enabling rapid response and halting propagation.
Impact at a Glance
Affected Business Functions
- Software Development
- IT Operations
Estimated downtime: 5 days
Estimated loss: $500,000
Potential exposure of developer credentials, source code, and sensitive project data.
Recommended Actions
Key Takeaways & Next Steps
- • Deploy zero trust segmentation to enforce least privilege at the workload, application, and identity level across all cloud environments.
- • Implement east-west traffic controls with microsegmentation to contain the spread of self-propagating threats and limit lateral movement.
- • Enforce rigorous egress filtering and cloud firewall policies to block unauthorized outbound connections and prevent data exfiltration.
- • Monitor for network anomalies and unknown behaviors using real-time threat detection integrated with cloud-native observability tools.
- • Establish continuous, automated policy enforcement using a unified security fabric to enable rapid isolation and response to novel supply chain threats.
