Which versions of env-express are malicious?

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

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

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

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

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

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

Malicious package

env-expressnpm

Advisory published Mar 24, 2026Updated Apr 7, 2026

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

MAL-2026-2361

Immediate action

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

npm uninstall env-express

What this malware does

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

Malicious versions

1 flagged

2.5.5

Indicators of compromise (SHA-256)

bd2ed62a252fd0eb1e793842d6f039a6a6b2053866835c97129e32fae2f99e86

641ecb34e7cfa3af77893add29d18b3c9c1e2b95012ff76c775a7bd8ca97ea4b

Detection & response playbook

Malicious package

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

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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