Which versions of env-expanded are malicious?

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

How do I remediate env-expanded if I installed it?

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

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

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

Search your lockfiles and build artifacts for env-expanded (version 2.5.5).

Malicious package

env-expandednpm

Advisory published Mar 24, 2026Updated Apr 7, 2026

env-expanded is a confirmed malicious npm package (MAL-2026-2360) 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 env-expanded (npm)

MAL-2026-2360

Immediate action

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

npm uninstall env-expanded

What this malware does

The package env-expanded was found to contain malicious code.

Malicious versions

1 flagged

2.5.5

Indicators of compromise (SHA-256)

7efcffa09f225d99d90dbb6ee9ec32135ef87b362f76bb4b7096133d097b143d

d3b59507cce21e48b0df323a7a5cedf303427c72c2118fdc15702c813174cfa8

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for env-expanded (version 2.5.5).
If you installed it — respond
Remove env-expanded 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 env-expanded 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. env-expanded 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-01754

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks env-expanded-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