GlassWorm: Malicious VS Code Extensions Trigger a New Wave of Supply-Chain Attacks
Executive Summary
In late 2025, cybersecurity researchers discovered the 'GlassWorm' malware campaign actively targeting the Visual Studio Code (VS Code) ecosystem via three malicious extensions available on the official marketplace. With over 7,400 combined downloads, these extensions enabled threat actors to inject malware directly into developers' environments, facilitating credential theft, remote access, and potential downstream supply-chain attacks. Attackers leveraged trusted community tools as the entry vector, bypassing traditional perimeter defenses to gain a foothold in development workflows and potentially propagate malware throughout interconnected repositories.
This incident underscores the rising prevalence of supply-chain attacks in the software development ecosystem and the unique risks posed by compromised IDE extensions. The popularity of VS Code amplifies the potential blast radius, highlighting an urgent need for improved extension vetting, granular access controls, and continuous threat monitoring within CI/CD pipelines.
Why This Matters Now
As organizations increasingly rely on third-party and open-source developer tools, the risk of malicious extensions compromising entire supply chains is at an all-time high. The GlassWorm campaign demonstrates how attackers can weaponize popular platforms to reach thousands of victims swiftly, making immediate vigilance, improved vetting, and zero trust controls within development environments critical.
Attack Path Analysis
Attackers distributed malicious VS Code extensions via supply chain compromise, tricking users into installing seemingly legitimate tools. Once installed, the malware likely leveraged elevated permissions granted to extensions to escalate privileges and further entrench itself on developer systems or connected cloud resources. The threat then used internal cloud or network APIs, or developer credentials, to move laterally into other environments. After establishing persistent command and control via encrypted outbound connections, the malware exfiltrated data or credentials over secured or obfuscated channels. Finally, the operation resulted in business impact such as data leakage, further compromise of downstream environments, or use of stolen access in follow-on attacks.
Kill Chain Progression
Initial Compromise
Description
Malicious VS Code extensions were published and installed by unsuspecting users, enabling attacker code execution on developer endpoints and potentially their connected cloud environments.
Related CVEs
CVE-2025-49714
CVSS 7.8A trust boundary violation in the Microsoft Python extension for Visual Studio Code allows an unauthorized attacker to execute code locally.
Affected Products:
Microsoft Python extension for Visual Studio Code – < 2025.7.8
Exploit Status:
no public exploitReferences:
CVE-2024-49049
CVSS 7.1Improper access control in the Visual Studio Code Remote Extension allows an attacker with local access and low privileges to potentially elevate their permissions without requiring user interaction.
Affected Products:
Microsoft Visual Studio Code Remote Extension – < 0.115.1
Exploit Status:
no public exploitReferences:
MITRE ATT&CK® Techniques
Supply Chain Compromise: Compromise Software Dependencies and Development Tools
Compromise Client Software Binary
Command and Scripting Interpreter: Windows Command Shell
Event Triggered Execution: Application Shimming
Hijack Execution Flow: DLL Side-Loading
Application Layer Protocol: Web Protocols
Obfuscated Files or Information
Potential Compliance Exposure
Mapping incident impact across multiple compliance frameworks.
PCI DSS 4.0 – Ensure integrity of security mechanisms, processes, and tools
Control ID: 6.2.2
NYDFS 23 NYCRR 500 – Cybersecurity Policy
Control ID: 500.03
DORA – ICT Risk Management Framework
Control ID: Art. 6(1)
CISA ZTMM 2.0 – Monitor and Secure Development & Deployment Pipelines
Control ID: Supply Chain Integrity 2.C
NIS2 Directive – Supply Chain Security
Control ID: Article 21(2)(d)
Sector Implications
Industry-specific impact of the vulnerabilities, including operational, regulatory, and cloud security risks.
Computer Software/Engineering
Direct supply-chain attack targeting VS Code extensions compromises development environments, threatening code integrity and enabling lateral movement within software organizations.
Information Technology/IT
GlassWorm malware in development tools creates east-west traffic security risks, requiring zero trust segmentation and enhanced threat detection capabilities.
Financial Services
Compromised developer environments pose data exfiltration risks to sensitive financial data, necessitating egress security controls and encrypted traffic monitoring.
Health Care / Life Sciences
Supply-chain compromise threatens HIPAA compliance through potential lateral movement and data breach risks in healthcare development and IT infrastructure.
Sources
- GlassWorm Malware Discovered in Three VS Code Extensions with Thousands of Installshttps://thehackernews.com/2025/11/glassworm-malware-discovered-in-three.htmlVerified
- GlassWorm Returns with 24 Malicious Extensions Impersonating Popular Developer Toolshttps://thehackernews.com/2025/12/glassworm-returns-with-24-malicious.htmlVerified
- 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
- GlassWorm Malware Uses Hidden Code to Compromise VS Code Extensions on OpenVSXhttps://cyberpress.org/glassworm-malware/Verified
Frequently Asked Questions
Cloud Native Security Fabric Mitigations and ControlsCNSF
Zero Trust Segmentation, east-west traffic security, rigorous egress controls, and advanced threat detection could have contained the attack at multiple stages, limiting lateral movement, detecting malicious behaviors, and blocking data exfiltration or C2 activity. Proper network workload isolation and visibility would have reduced the attacker's ability to persist and spread within cloud environments.
Control: Cloud Native Security Fabric (CNSF)
Mitigation: Real-time policy enforcement on ingress could flag or stop untrusted extension traffic.
Control: Zero Trust Segmentation
Mitigation: Segmentation restricts movement, limiting an attacker's ability to exploit elevated privileges.
Control: East-West Traffic Security
Mitigation: Internal traffic visibility and control block unauthorized workload-to-workload communications.
Control: Egress Security & Policy Enforcement
Mitigation: Outbound C2 connections are detected or blocked, disrupting attacker command channels.
Control: Cloud Firewall (ACF)
Mitigation: Policy-driven rules and egress inspection prevent unauthorized data from leaving the managed network.
Rapid detection of anomalous behaviors allows swift containment to minimize organizational impact.
Impact at a Glance
Affected Business Functions
- Software Development
- Version Control
- Package Management
Estimated downtime: 5 days
Estimated loss: $500,000
Potential exposure of source code, developer credentials, and sensitive project data due to compromised Visual Studio Code extensions.
Recommended Actions
Key Takeaways & Next Steps
- • Institute rigorous Zero Trust Segmentation and least-privilege policies for cloud workloads and developer systems.
- • Deploy comprehensive east-west traffic security and workload-level microsegmentation to detect and block lateral attacker movement.
- • Enforce strict egress controls, with domain and application-based filtering, to prevent malicious outbound connections and stop C2 or exfiltration attempts.
- • Implement real-time threat detection and anomaly response across all cloud segments to rapidly identify and remediate suspicious behaviors.
- • Ensure continuous visibility and policy governance for cloud-native resources, focusing on supply chain and developer tool exposures.
