Which versions of dotenv-nodejs are malicious?

The following npm versions of dotenv-nodejs are flagged malicious: 3.3.5. Treat any of these as compromised.

How do I remediate dotenv-nodejs if I installed it?

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

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

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

Search your lockfiles and build artifacts for dotenv-nodejs (version 3.3.5).

Malicious package

dotenv-nodejsnpm

Advisory published Mar 18, 2026Updated Mar 23, 2026

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

Malicious code in dotenv-nodejs (npm)

MAL-2026-1715

Immediate action

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

npm uninstall dotenv-nodejs

What this malware does

The package dotenv-nodejs was found to contain malicious code.

Malicious versions

1 flagged

3.3.5

Indicators of compromise (SHA-256)

db51811f933b3bde49c2cf469520becf69eeb5654d4626b8d5579fcd175f132b

14a15bdceba2f650e2c3d04e2be33994e406c2548812e89a520fc511c2529266

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-01258

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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