Which versions of env-node-cli are malicious?

The following npm versions of env-node-cli are flagged malicious: 2.5.5. Treat any of these as compromised.

How do I remediate env-node-cli if I installed it?

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

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

Yes — env-node-cli is associated with the RLMA-2026-01758 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 env-node-cli across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for env-node-cli (version 2.5.5).

Malicious package

env-node-clinpm

Advisory published Mar 24, 2026Updated Apr 7, 2026

env-node-cli is a confirmed malicious npm package (MAL-2026-2364) that executes malicious code on install (malicious version 2.5.5). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in env-node-cli (npm)

MAL-2026-2364

Immediate action

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

npm uninstall env-node-cli

What this malware does

The package env-node-cli was found to contain malicious code.

Malicious versions

1 flagged

2.5.5

Indicators of compromise (SHA-256)

84b40f149390b8a2bc35b579042d6fef3ebd93e6093935c74dd62e18aa941638

0b1b6f1e45cba2962a0ff258e15bc55427bc91725fb41409442324f1a19cf520

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-01758

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks env-node-cli-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