Malicious Code Detected in allbook Package - Security Alert

allbook Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-14320: Malicious code in allbook (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 Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The allbook package is an npm library designed for managing and organizing book collections. It offers features such as adding, removing, and searching for books, making it a useful tool for developers working on library management systems. However, this package has been found to contain malicious code, posing significant security risks to users who integrate it into their applications.

Vulnerability Detail

The vulnerability in the allbook package stems from the inclusion of malicious code that can compromise the security of applications utilizing this library. This code may lead to unauthorized access, data breaches, or other harmful actions within the affected systems. The issue was introduced in version 0 and affects all subsequent versions, making it critical for users to take immediate action to mitigate potential risks.

How To Fix

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

npm uninstall allbook

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 measure, users can remove the allbook package from their projects until a secure version is released. This can be done using the command: 'npm uninstall allbook'. Additionally, consider using alternative packages that provide similar functionality without the security risks.

Conclusion

The discovery of malicious code in the allbook package highlights the importance of maintaining secure coding practices and monitoring dependencies for vulnerabilities. Users are urged to take immediate action by updating or removing the package to protect their applications.

See every vulnerability recorded for allbook →

Share this vulnerability

FAQ

The allbook package is an npm library designed for managing book collections, allowing users to add, remove, and search for books.

The malicious code can potentially lead to unauthorized access and data breaches within applications that use the allbook package.

You can use Vulert, which monitors open-source vulnerabilities in real-time. Simply upload your package-lock.json file to receive alerts about vulnerabilities.

Yes, you can uninstall the allbook package and look for alternative libraries that provide similar functionalities without the associated risks.

Regularly check for updates on your packages and consider using tools like Vulert to monitor vulnerabilities in your projects.

How To Fix

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

npm uninstall allbook

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