Critical Malicious Code Vulnerability in bootsnap Package

bootsnap Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-15984: Malicious code in bootsnap (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 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 bootsnap package is a performance optimization tool for Ruby applications, designed to speed up boot times by caching expensive computations. It is widely used in the Ruby on Rails ecosystem to enhance application performance. However, recent findings have revealed that the package contains malicious code, posing significant security risks to applications that rely on it.

Vulnerability Detail

The bootsnap package has been identified to contain malicious code that can compromise the security of applications using it. This vulnerability originated from a compromised version of the package, which was introduced in version 0 and has the potential to execute harmful actions within the application environment. The ramifications of this vulnerability include unauthorized access to sensitive data, potential data breaches, and the ability for attackers to manipulate application behavior.

How To Fix

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

npm uninstall bootsnap

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, you may consider removing the bootsnap package from your project until a secure version is confirmed. You can do this by executing: 'npm uninstall bootsnap'. This will prevent any malicious code from executing while you seek a secure alternative or wait for an update.

Conclusion

The discovery of malicious code in the bootsnap package poses a serious threat to applications utilizing it. It is essential to take immediate action by updating to a secure version or removing the package to safeguard your application from potential attacks. Utilizing tools like Vulert can help monitor and alert for such vulnerabilities in real-time.

See every vulnerability recorded for bootsnap →

Share this vulnerability

FAQ

Bootsnap is used to optimize boot times for Ruby applications by caching expensive computations.

You can check if your application is affected by using Vulert, which monitors open-source vulnerabilities in real-time. Visit Vulert Scanner to analyze your package-lock.json without any signup.

The malicious code can lead to unauthorized access to sensitive data, data breaches, and manipulation of application behavior.

Yes, a patched version of the bootsnap package is available. It is recommended to update to the latest version to mitigate the risk.

If immediate updates are not possible, consider removing the bootsnap package from your project as a temporary measure.

How To Fix

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

npm uninstall bootsnap

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