Which versions of dotenv-node-promised are malicious?

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

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

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

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

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

Search your lockfiles and build artifacts for dotenv-node-promised (version 2.3.5).

Malicious package

dotenv-node-promisednpm

Advisory published Mar 18, 2026Updated Mar 23, 2026

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

Malicious code in dotenv-node-promised (npm)

MAL-2026-1714

Immediate action

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

npm uninstall dotenv-node-promised

What this malware does

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

Malicious versions

1 flagged

2.3.5

Indicators of compromise (SHA-256)

17a79ffa37a096da5e9b57e45d401110f0119005e0dedab7fa912ee4f676657d

df463afbbda6fbe8da01a353fbc7c385b9e136cb2315e85b08bf2af29947fe8c

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-01257

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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