Which versions of vscode-component-explorer are malicious?

The following npm versions of vscode-component-explorer are flagged malicious: 99.9.9, 99.9.15. Treat any of these as compromised.

How do I remediate vscode-component-explorer if I installed it?

Remove vscode-component-explorer from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

I already installed vscode-component-explorer — how do I know if it already compromised me?

If vscode-component-explorer was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is vscode-component-explorer part of a known attack campaign?

Yes — vscode-component-explorer is associated with the RLMA-2026-05355, RLUA-2026-06542 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find vscode-component-explorer across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for vscode-component-explorer (2 malicious versions).

Malicious package

vscode-component-explorernpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

vscode-component-explorer is a confirmed malicious npm package (MAL-2026-7432) that executes malicious code on install (malicious versions 99.9.9, 99.9.15). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in vscode-component-explorer (npm)

MAL-2026-7432

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall vscode-component-explorer

Malicious versions

2 flagged

99.9.999.9.15

Indicators of compromise (SHA-256)

ae8bf71aeb528868b3be291309f2406e0f8a31c20f806c6615fb6fe929383ce1

0e42e015b46cd3e4cb5771cd67c373b68930076b5b4d8425a7d27aa01cf62190

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for vscode-component-explorer (2 malicious versions).
If you installed it — respond
Remove vscode-component-explorer from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If vscode-component-explorer was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. vscode-component-explorer on npm has been identified as a malicious package (versions 99.9.9, 99.9.15 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2026-05355RLUA-2026-06542

References

github.com

Credits

ReversingLabs · finder

Detect & block this

O3 blocks vscode-component-explorer-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database