Critical Malicious Code Vulnerability in @fishingbooker/react-loader Package

@fishingbooker/react-loader Updated 25 Nov 2025

Summary

24/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-191221: Malicious code in @fishingbooker/react-loader (npm). Affects @fishingbooker/react-loader versions 1.0.7. No fix is published. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The @fishingbooker/react-loader package is a JavaScript library designed for use in React applications, providing a simple way to implement loading indicators. However, this package has been compromised, leading to significant security concerns. The vulnerability allows malicious code to execute, potentially compromising user data and system integrity.

Vulnerability Detail

The vulnerability originates from a malicious payload introduced by the Sha1-Hulud: The Second Coming NPM worm. This worm is capable of stealing tokens and credentials, publishing them to GitHub, and propagating itself to other NPM packages owned by the user. Additionally, it may establish persistence through GitHub actions and could even destroy the user's home directory. Any system running this package should be considered fully compromised.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall @fishingbooker/react-loader

If it arrived as a transitive dependency, remove the package that pulled it in, then reinstall.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Workaround

There are no effective workarounds for this vulnerability. The only recommended action is to uninstall the compromised package and ensure that all sensitive information is secured.

Conclusion

The @fishingbooker/react-loader package has been compromised, leading to a critical vulnerability that can severely impact system security. Immediate action is required to mitigate risks, including uninstalling the package and securing sensitive information. Regular monitoring for vulnerabilities is essential to maintain application security.

See every vulnerability recorded for @fishingbooker/react-loader →

Share this vulnerability

FAQ

You should immediately uninstall the package and rotate any secrets or keys stored on your system.

You can use Vulert's playground at Vulert Scanner to check if your application is affected without needing to sign up.

Failure to address this vulnerability can lead to unauthorized access to sensitive data, potential data loss, and further propagation of malicious code.

Currently, there is no patched version available. The best course of action is to uninstall the package.

The malicious code was introduced by the Sha1-Hulud: The Second Coming NPM worm, which compromises systems and steals sensitive information.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall @fishingbooker/react-loader

If it arrived as a transitive dependency, remove the package that pulled it in, then reinstall.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback