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

@fishingbooker/react-loadernpm

Advisory published Updated

@fishingbooker/react-loader is a confirmed malicious npm package (MAL-2025-191221) that steals credentials and exfiltrates sensitive data (malicious version 1.0.7). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @fishingbooker/react-loader (npm)

MAL-2025-191221
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall @fishingbooker/react-loader

What this malware does

The package @fishingbooker/react-loader 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
1.0.7

Indicators of compromise (SHA-256)

803270c04d149e4abaf5f9913b24c64d7504fbd5ed713073a1412adc62a33183
b056d4b489b76da81da3d80ccd9e32859284bd6db8d2d0ccbfb241e033cd875a
90a19dbfbd7292340e4857d9c40d537185efb1402a471df4b8346b4ae3575d3f
fc72fd52ca850c10b694f9e2ca57fe1ea1239285d872edffc768ea6fd0f2cde0

Detection & response playbook

Credential / info stealer
  1. Find it

    Search your lockfiles and build artifacts for @fishingbooker/react-loader (version 1.0.7).

  2. If you installed it — respond

    @fishingbooker/react-loader 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 @fishingbooker/react-loader 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. @fishingbooker/react-loader on npm has been identified as a malicious package (version 1.0.7 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-pqh4-9mxj-w73cRLMA-2025-06020

References

Credits

  • Amazon Inspector · finder
  • ReversingLabs · finder

Detect & block this

O3 blocks @fishingbooker/react-loader-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Explore

@fishingbooker/react-loader (npm) malicious package — MAL-2025-191221 | O3 Security