Which versions of collect-rangers are malicious?

The following npm versions of collect-rangers are flagged malicious: 9999.0.0. Treat any of these as compromised.

How do I remediate collect-rangers if I installed it?

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

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

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

Search your lockfiles and build artifacts for collect-rangers (version 9999.0.0).

Malicious package

collect-rangersnpm

Advisory published Apr 16, 2026Updated Apr 23, 2026

collect-rangers is a confirmed malicious npm package (MAL-2026-2748) that executes malicious code on install (malicious version 9999.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in collect-rangers (npm)

MAL-2026-2748

Immediate action

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

npm uninstall collect-rangers

What this malware does

The package collect-rangers was found to contain malicious code.

Malicious versions

1 flagged

9999.0.0

Indicators of compromise (SHA-256)

c019361415b342ba1a657f822f494df7c6240cb75144ad57e3b40b755a02936c

2032d1a91a275e0d014941f9efbffde4e402db99abfb381c36335c75f7f78902

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-01927

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks collect-rangers-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