Which versions of redux-router-kit are malicious?

The following npm versions of redux-router-kit are flagged malicious: 1.2.2, 1.2.3, 1.2.4. Treat any of these as compromised.

How do I remediate redux-router-kit if I installed it?

redux-router-kit is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed redux-router-kit — how do I know if it already compromised me?

If redux-router-kit was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is redux-router-kit part of a known attack campaign?

Yes — redux-router-kit is associated with the GHSA-83f2-m5xj-79wx 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 redux-router-kit across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for redux-router-kit (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging redux-router-kit across your stack and pipelines.

Malicious package

redux-router-kitnpm

Malicious code in redux-router-kit (npm) Remove it immediately and rotate any exposed credentials.

MAL-2025-190780

Immediate action

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

npm uninstall redux-router-kit

What this malware does

The package redux-router-kit was found to contain malicious code.

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

This package was compromised by the Sha1-Hulud: The Second Coming NPM worm. The malicious payload steals tokens and credentials and publishes them to GitHub. The worm will propogate itself to NPM packages the user owns and establish persistence is a GitHub action. The package may also destroy the user's home directory.

Malicious versions

3 flagged

1.2.21.2.31.2.4

Indicators of compromise (SHA-256)

6714063bc703d6750a4f6a6eedaa083372d15b7b9fa6eef3c58492ac74792b9a

d3336c78dffab3cf95e60180dad5e67109d7de3e5dbfc888d10874c466a4088c

20aaee0478efa9fe60248f8ae3d7dd4c6e293a8b1a29795d4f03a37bbf067879

8945a1600d6443a04709f2723b40f1e2478a77236dd3d39fc2ad1918bd9c4eb7

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for redux-router-kit (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging redux-router-kit across your stack and pipelines.
If you installed it — respond
redux-router-kit is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If redux-router-kit was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks redux-router-kit before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. redux-router-kit on npm has been identified as a malicious package (versions 1.2.2, 1.2.3, 1.2.4 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-83f2-m5xj-79wx

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks redux-router-kit-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring