GlassWorm VS Code Extensions Spread Self-Propagating Malware via Open VSX

Security researchers have observed a persistent escalation of the GlassWorm campaign, in which threat actors publish seemingly innocuous extensions for Visual Studio Code on the Open VSX registry. The rogue extensions, once installed, quietly inject self‑propagating malware into developer workstations, turning trusted IDE environments into launchpads for further attacks.

The malicious code is hidden inside extension entry points and uses obfuscated JavaScript to evade static‑analysis tools. Upon execution, it contacts a remote command‑and‑control server, downloads additional payloads, and can replicate itself by modifying other installed extensions or injecting scripts into project files. The malware also harvests environment variables, API keys, and source‑control credentials, providing attackers with a foothold in downstream code repositories.

The campaign underscores the growing supply‑chain risk associated with open‑source extension marketplaces. Because VS Code extensions are granted extensive permissions—including file system access and network communication—a single compromised package can compromise an entire development pipeline. Researchers note that the extensions have already been downloaded thousands of times before detection, raising concerns about a wide‑reaching breach of trust.

Organizations are advised to enforce strict extension‑approval processes, verify publisher identities, and employ code‑signing policies for all IDE plugins. Continuous monitoring for anomalous network traffic, endpoint telemetry, and the use of static‑analysis scanners can help identify the malicious behavior early. By treating extension stores as a critical attack surface, teams can mitigate the risk posed by GlassWorm and similar supply‑chain threats.