Critical Malicious Code Vulnerability in booksuite Package

booksuite Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-15963: Malicious code in booksuite (npm). Affected versions are not published. 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 Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The booksuite package is a Node.js library designed for managing and organizing book-related data, offering functionalities such as cataloging, searching, and retrieving information about books. It is widely used in applications that require book management features. However, the package has been identified to contain malicious code that poses significant security risks to applications utilizing it.

Vulnerability Detail

The vulnerability in the booksuite package stems from the inclusion of malicious code that can compromise the security of applications using this library. This code can lead to unauthorized access, data breaches, or other malicious activities. The issue was introduced in version 0 and affects all subsequent versions, making it critical for users to address this vulnerability promptly.

How To Fix

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

npm uninstall booksuite

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 temporary workaround, users can remove the booksuite package from their project until a secure version is released. This can be done using the command: npm uninstall booksuite. Alternatively, consider using a different package that provides similar functionality without the associated risks.

Conclusion

The discovery of malicious code in the booksuite package highlights the importance of regularly monitoring and updating dependencies in software projects. Users are urged to take immediate action to mitigate risks associated with this vulnerability by updating or removing the affected package.

See every vulnerability recorded for booksuite →

Share this vulnerability

FAQ

The malicious code can lead to unauthorized access and potential data breaches in applications using the booksuite package.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without needing to sign up.

Users should check the package repository for any patched versions of booksuite and update accordingly.

Consider removing the booksuite package from your project or using an alternative package until a secure version is available.

Vulert uses the package-lock.json file to monitor and alert for open-source vulnerabilities in your software, providing real-time insights.

How To Fix

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

npm uninstall booksuite

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