Which versions of redirect-clrm2u are malicious?

The following npm versions of redirect-clrm2u are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate redirect-clrm2u if I installed it?

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

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

Yes — redirect-clrm2u is associated with the RLMA-2025-05934 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 redirect-clrm2u across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for redirect-clrm2u (version 1.0.0).

Malicious package

redirect-clrm2unpm

Advisory published Dec 1, 2025Updated Dec 2, 2025

redirect-clrm2u is a confirmed malicious npm package (MAL-2025-191584) that executes malicious code on install (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in redirect-clrm2u (npm)

MAL-2025-191584

Immediate action

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

npm uninstall redirect-clrm2u

What this malware does

The package redirect-clrm2u was found to contain malicious code.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

ed8269d78ac65d769d647ea56e9132d9ffa9db7393202ecaa045770310a241cb

eb5bc4c8ac14d2756734e3141b0d58c139b52fe3338990559e143ec06222600a

Detection & response playbook

Malicious package

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

Campaign

RLMA-2025-05934

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks redirect-clrm2u-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