NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
Malicious package

redux-forgenpm

Advisory published Updated

redux-forge is a confirmed malicious npm package (MAL-2025-190701) that steals credentials and exfiltrates sensitive data (malicious version 2.5.3). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in redux-forge (npm)

MAL-2025-190701
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall redux-forge

What this malware does

The package redux-forge 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

1 flagged
2.5.3

Indicators of compromise (SHA-256)

f80cb61ec8f9b4f1ee385b40c40e1816cb61a012074ddc792d16f433c6a32294
4ab662afde2ebe0d7c2a8537b2bdab8226b61daf75ff4e54ad51bf5bb7eee8eb
53104b3974b3f906980cbf9e9170f8d78ae17f95436bcc129de382af7bc0ff7a
7d850e200cb92510b336c403b3d89910ee9ed0450403e09f69dc2168e1631620

Detection & response playbook

Credential / info stealer

  1. Find it

    Search your lockfiles and build artifacts for redux-forge (version 2.5.3).

  2. If you installed it — respond

    redux-forge 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.

  3. Did it already run?

    If redux-forge 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. redux-forge on npm has been identified as a malicious package (version 2.5.3 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-mrqr-92qq-v899

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks redux-forge-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

Explore

All malware advisories How O3 detects malware Vulnerability database
redux-forge (npm) malicious package — MAL-2025-190701 | O3 Security