Which versions of dotenvx-int are malicious?

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

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

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

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

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

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

Malicious package

dotenvx-intnpm

Advisory published Mar 18, 2026Updated Mar 23, 2026

dotenvx-int is a confirmed malicious npm package (MAL-2026-1717) 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 dotenvx-int (npm)

MAL-2026-1717

Immediate action

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

npm uninstall dotenvx-int

What this malware does

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

Malicious versions

1 flagged

3.5.5

Indicators of compromise (SHA-256)

829a29f754880bffe88d89dc1029b5c8593bf9cab3f41d90f83031268309c662

353c7d76c07eade885f2ae9f5d2b6c763f3238a7200901cf48a3f00f3b74d048

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for dotenvx-int (version 3.5.5).
If you installed it — respond
Remove dotenvx-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 dotenvx-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. dotenvx-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-01261

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks dotenvx-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