Which versions of express-ranges are malicious?

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

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

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

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

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

Search your lockfiles and build artifacts for express-ranges (version 3.7.7).

Malicious package

express-rangesnpm

Advisory published Mar 18, 2026Updated Mar 23, 2026

express-ranges is a confirmed malicious npm package (MAL-2026-1732) that executes malicious code on install (malicious version 3.7.7). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in express-ranges (npm)

MAL-2026-1732

Immediate action

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

npm uninstall express-ranges

What this malware does

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

Malicious versions

1 flagged

3.7.7

Indicators of compromise (SHA-256)

6766596a6256748f902dd5ac2bcec89f4d9d10a127e788e8289ce827c0aa6c5d

72e2924456833204b2201e4c108e394c45b7f35695aa2bb4a1048528ef95b78e

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-01309

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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