Which versions of dotenv-int are malicious?

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

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

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

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

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

Search your lockfiles and build artifacts for dotenv-int (version 3.5.5).

Malicious package

dotenv-intnpm

Advisory published Mar 18, 2026Updated Mar 23, 2026

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

Malicious code in dotenv-int (npm)

MAL-2026-1711

Immediate action

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

npm uninstall dotenv-int

What this malware does

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

Malicious versions

1 flagged

3.5.5

Indicators of compromise (SHA-256)

92371211679e4811dce5d678a9b61a3e2aa60e12bc677df717223024954f2ff8

5ff3b8c2dda09766587481490c9be74a1af10a9660698a8f7b8f31a7df47bc96

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-01252

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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