Which versions of dotenv-cli-node are malicious?

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

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

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

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

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

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

Malicious package

dotenv-cli-nodenpm

Advisory published Mar 18, 2026Updated Mar 23, 2026

dotenv-cli-node is a confirmed malicious npm package (MAL-2026-1710) 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 dotenv-cli-node (npm)

MAL-2026-1710

Immediate action

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

npm uninstall dotenv-cli-node

What this malware does

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

Malicious versions

1 flagged

2.4.5

Indicators of compromise (SHA-256)

2b19cb30c02228173e0072ae436ce1d5e0c2f6eb6f9f7fa08755075813d6d63f

914751db31692fb4c83c9e8e3e2fed123b349d261368499b9caf33dc411b62cd

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for dotenv-cli-node (version 2.4.5).
If you installed it — respond
Remove dotenv-cli-node 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 dotenv-cli-node 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. dotenv-cli-node 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-01247

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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