Which versions of redirect-5k9q5v are malicious?

The following npm versions of redirect-5k9q5v are flagged malicious: 1.0.1. Treat any of these as compromised.

How do I remediate redirect-5k9q5v if I installed it?

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

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

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

Search your lockfiles and build artifacts for redirect-5k9q5v (version 1.0.1).

Malicious package

redirect-5k9q5vnpm

Advisory published Dec 1, 2025Updated Dec 2, 2025

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

Malicious code in redirect-5k9q5v (npm)

MAL-2025-191583

Immediate action

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

npm uninstall redirect-5k9q5v

What this malware does

The package redirect-5k9q5v was found to contain malicious code.

Malicious versions

1 flagged

1.0.1

Indicators of compromise (SHA-256)

d263ced21a9efcc02d9a6711c94763fd074add8fad58db4fd96da3d5c2578ca3

cbc038d322ab58ef55f9713dd3250ed8acb58c774ff1690a234afcdac30d4bb5

Detection & response playbook

Malicious package

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

Campaign

RLMA-2025-05933

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks redirect-5k9q5v-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