ACVE-2026-0413
GlassWorm extensions target developer credentials across IDEs
Part of campaign: GlassWorm
In the wild
Description
What
GlassWorm distributed malicious VS Code and Open VSX extensions, including code-wakatime-activity-tracker, and later related npm and PyPI artifacts. The campaign targeted npm, GitHub, and wallet credentials and used Node RAT and SOCKS infrastructure. Public install figures are exposure measures, not a count of compromised developers.
Which configuration is exposed
The exposed configuration enables the named extension in VS Code, Cursor, Windsurf, or VSCodium. These IDEs give extension code a developer workstation context, so the supply-chain boundary exists even when the model and agent approval settings are restrictive.
How ACVE detects it
ACVE matches the extension name and open-vsx marketplace. It cannot inspect extension contents or infer whether the user opened a project while the malicious code was active. A different extension identifier or marketplace requires separate review.
Fix
Remove the extension and related artifacts, rotate npm, GitHub, cloud, SSH, and wallet credentials, and inspect for SOCKS or RAT persistence. Restrict extension installation to reviewed publishers and retain package hashes for future audits.
Grounding needed
The CrowdStrike and news sources should be checked for the extension list, campaign dates, and takedown claims. The install figure is preserved as a range because it is not a victim count.
This record is limited to the condition named in the public source: GlassWorm extensions target developer credentials across IDEs. A match is a review signal for that condition, not a claim that every installation, package, model, or host was compromised. Operators should preserve the resolved evidence and investigate adjacent credentials, network exposure, and execution history before closing the finding. The result should be retained with the lock snapshot used for the match so later review can distinguish configuration drift from a changed public record.
Configuration
some plugins where
and
name eq "code-wakatime-activity-tracker"
marketplace eq "open-vsx"Fix
Remove GlassWorm extensions and rotate developer credentials.
- Remove
AgentPlugin:code-wakatime-activity-tracker@open-vsx. - Reconfigure
plugins. Allow only reviewed extension publishers.
Validation
No validation entries recorded.
Grounding
No grounding checks recorded.
References
No references recorded.
Report a problemValidate this advisoryDiscussJSONEdit on GitHub