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

Summary

24/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-191222: Malicious code in @fishingbooker/react-pagination (npm). Affects @fishingbooker/react-pagination versions 2.0.6. 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 Devnack Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The @fishingbooker/react-pagination package is a JavaScript library designed for implementing pagination in React applications. It provides developers with an easy way to manage and display paginated data. However, this package has been compromised, leading to severe security risks for any application using it.

Vulnerability Detail

The vulnerability stems from a malicious code injection within version 2.0.6 of the @fishingbooker/react-pagination package. This package was compromised by the Sha1-Hulud: The Second Coming NPM worm, which is capable of stealing tokens and credentials, publishing them to GitHub, and propagating itself to other NPM packages owned by the user. The worm also has the potential to destroy the user's home directory, making it a critical security threat.

How To Fix

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

npm uninstall @fishingbooker/react-pagination

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

As a workaround, you can temporarily replace the functionality provided by the @fishingbooker/react-pagination package with a custom pagination implementation or another trusted pagination library until a secure version is available.

Conclusion

The @fishingbooker/react-pagination package has been compromised, posing significant security risks to applications that utilize it. Immediate action is required to remove the package and secure any potentially compromised credentials. Utilizing tools like Vulert can help in monitoring for such vulnerabilities in the future.

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

Share this vulnerability

FAQ

You should uninstall the package immediately and rotate any secrets or keys that may have been compromised.

You can use Vulert to monitor and alert in real-time for open-source vulnerabilities. Visit Vulert Scanner to check if your application is affected without requiring access to the code or installation.

The risks include unauthorized access to sensitive tokens and credentials, potential data loss, and the propagation of malicious code to other packages.

Currently, there is no patched version of the @fishingbooker/react-pagination package. It is recommended to remove the package and look for alternatives.

Regularly monitor your dependencies for vulnerabilities using tools like Vulert, and ensure to keep your packages updated to the latest secure versions.

How To Fix

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

npm uninstall @fishingbooker/react-pagination

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