Which versions of node-dotenv-cli are malicious?

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

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

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

If node-dotenv-cli was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is node-dotenv-cli part of a known attack campaign?

Yes — node-dotenv-cli is associated with the GHSA-46v6-58g3-h5qh, RLMA-2026-01459 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-dotenv-cli across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for node-dotenv-cli (version 2.4.5). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging node-dotenv-cli across your stack and pipelines.

Malicious package

node-dotenv-clinpm

Malicious code in node-dotenv-cli (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-853

Immediate action

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

npm uninstall node-dotenv-cli

What this malware does

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

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

Malicious versions

1 flagged

2.4.5

Indicators of compromise (SHA-256)

5bb66069e2bde985ae448962eaaf6373cd54aa2cd51fb20a0fef26ecb5dee2d5

76b47bebee6a74c00d3be10fad072e05074a62b29205377f682463290bad39c3

d8466e099ba099035a2b059744003b908812da9e81f7dc162bedda0f56e332e1

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for node-dotenv-cli (version 2.4.5). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging node-dotenv-cli across your stack and pipelines.
If you installed it — respond
Remove node-dotenv-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 node-dotenv-cli was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks node-dotenv-cli before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. node-dotenv-cli 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

GHSA-46v6-58g3-h5qhRLMA-2026-01459

References

github.com

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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