Which versions of redux-forge are malicious?

The following npm versions of redux-forge are flagged malicious: 2.5.3. Treat any of these as compromised.

How do I remediate redux-forge if I installed it?

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.

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

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

Yes — redux-forge is associated with the GHSA-mrqr-92qq-v899 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-forge 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-forge (version 2.5.3). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging redux-forge across your stack and pipelines.

Malicious package

redux-forgenpm

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

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

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for redux-forge (version 2.5.3). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging redux-forge across your stack and pipelines.
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.
Did it already run?
If redux-forge 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-forge 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-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