Which versions of win-env-setup are malicious?

The following npm versions of win-env-setup are flagged malicious: 3.0.5, 3.0.6. Treat any of these as compromised.

How do I remediate win-env-setup if I installed it?

Remove win-env-setup 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 win-env-setup — how do I know if it already compromised me?

If win-env-setup 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 win-env-setup part of a known attack campaign?

Yes — win-env-setup is associated with the RLMA-2026-05366, RLUA-2026-06553 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 win-env-setup across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for win-env-setup (2 malicious versions).

Malicious package

win-env-setupnpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

win-env-setup is a confirmed malicious npm package (MAL-2026-7439) that executes malicious code on install (malicious versions 3.0.5, 3.0.6). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in win-env-setup (npm)

MAL-2026-7439

Immediate action

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

npm uninstall win-env-setup

Malicious versions

2 flagged

3.0.53.0.6

Indicators of compromise (SHA-256)

0a7c5cc0acc3309da6244321678fd67a072d222df4592f3d5b53b54dff2409b9

242a0886b7ce62097eb301f96fe8a0a80bf880c3af1c0800866de50638ae371a

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for win-env-setup (2 malicious versions).
If you installed it — respond
Remove win-env-setup 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 win-env-setup 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. win-env-setup on npm has been identified as a malicious package (versions 3.0.5, 3.0.6 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2026-05366RLUA-2026-06553

References

github.com

Credits

ReversingLabs · finder

Detect & block this

O3 blocks win-env-setup-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