Which versions of dotenv-xtend are malicious?

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

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

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

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

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

Search your lockfiles and build artifacts for dotenv-xtend (version 2.5.5).

Malicious package

dotenv-xtendnpm

Advisory published Mar 24, 2026Updated Apr 7, 2026

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

Malicious code in dotenv-xtend (npm)

MAL-2026-2351

Immediate action

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

npm uninstall dotenv-xtend

What this malware does

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

Malicious versions

1 flagged

2.5.5

Indicators of compromise (SHA-256)

756837cbde2a8789234a056da3107bee901ba4458607345bccb4e5ebfaddda03

d6523f1fff137b4db7fd0ed316a5d88d808ecb32bf0456c9977cdae82564f15d

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-01744

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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