Which versions of dotenv-mono-cli are malicious?

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

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

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

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

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

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

Malicious package

dotenv-mono-clinpm

Advisory published Mar 18, 2026Updated Mar 23, 2026

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

MAL-2026-1712

Immediate action

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

npm uninstall dotenv-mono-cli

What this malware does

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

Malicious versions

1 flagged

3.3.5

Indicators of compromise (SHA-256)

f2db83e17360c0f687f8338ec55e301e309a1f3c927aa55622c37246c2d6e8d1

78e4774845081c77828c11c246f1224738c74e91df84182defb19b32ff6a8757

Detection & response playbook

Malicious package

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

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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

Explore

All malware advisories How O3 detects malware Vulnerability database