Which versions of dotenv-plugin are malicious?

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

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

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

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

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

Search your lockfiles and build artifacts for dotenv-plugin (2 malicious versions).

Malicious package

dotenv-pluginnpm

Advisory published Mar 18, 2026Updated Mar 23, 2026

dotenv-plugin is a confirmed malicious npm package (MAL-2026-1716) that executes malicious code on install (malicious versions 2.3.5, 3.3.5). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in dotenv-plugin (npm)

MAL-2026-1716

Immediate action

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

npm uninstall dotenv-plugin

What this malware does

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

Malicious versions

2 flagged

2.3.53.3.5

Indicators of compromise (SHA-256)

7e18b05c76322d19af0b81b73e433b3622cc093d5ce22bac8fa5f4b8e12fb8ab

8c1892dd92715cddb9d2bc58111d6b2e4352677ff4d6b155ed7ddc9e04f06edf

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-01259

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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