Malicious Code Detected in Bootboot Package - Security Alert

bootboot Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-15968: Malicious code in bootboot (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 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 Bootboot package is an npm library designed for developers to streamline bootstrapping processes in JavaScript applications. It offers various functionalities aimed at enhancing productivity and efficiency in project setups. However, recent findings have revealed that this package contains malicious code, posing significant security risks to users and their applications.

Vulnerability Detail

The vulnerability in the Bootboot 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 malicious nature of the code was identified by security researchers, highlighting the importance of vigilance when using third-party packages.

How To Fix

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

npm uninstall bootboot

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, developers can consider using alternative packages that provide similar functionalities without the associated risks. It is advisable to thoroughly review the security history of any alternative packages before integration.

Conclusion

The discovery of malicious code in the Bootboot package underscores the importance of scrutinizing third-party libraries before use. Developers are urged to take immediate action to protect their applications by removing the affected package and considering secure alternatives. Utilizing tools like Vulert can further enhance security by providing real-time alerts for vulnerabilities.

See every vulnerability recorded for bootboot →

Share this vulnerability

FAQ

Bootboot is an npm library designed to assist developers in bootstrapping JavaScript applications efficiently.

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

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

It is crucial to remove the Bootboot package immediately and replace it with a secure alternative or wait for a patched version if available.

Regularly check your package-lock.json file with tools like Vulert to monitor for vulnerabilities in your open-source dependencies.

How To Fix

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

npm uninstall bootboot

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