Which versions of node-cli-dotenv are malicious?

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

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

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

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

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

Search your lockfiles and build artifacts for node-cli-dotenv (version 2.4.5).

Malicious package

node-cli-dotenvnpm

Advisory published Mar 18, 2026Updated Mar 23, 2026

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

Malicious code in node-cli-dotenv (npm)

MAL-2026-1802

Immediate action

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

npm uninstall node-cli-dotenv

What this malware does

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

Malicious versions

1 flagged

2.4.5

Indicators of compromise (SHA-256)

d7757907b93abdcf333df1acabc62406743b3b6f07f52504061ec764ba22d275

3b7df6bef20ed41b1a5c7e3ca57da4665f799cfcc6d6cf27b6dc87f8fa0560bc

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-01458

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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