Malicious Code in bootstrapper (npm)

bootstrapper Updated 02 Oct 2025

Summary

25/06/2024
CRITICAL
No i
Critical
Not published

MAL-2024-1833: Malicious code in bootstrapper (npm). Affects bootstrapper versions 35.0.0. 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 bootstrapper package is an npm package used for bootstrapping applications. It provides a set of tools and utilities to initialize and configure projects. The package is widely used in the JavaScript ecosystem for setting up project dependencies and configurations. However, a vulnerability has been identified in the bootstrapper package that involves the presence of malicious code in its bootstrapping process.

Vulnerability Detail

The vulnerability, identified as MAL-2024-1833, is a false positive caused by problematic ingestion. It was initially reported on June 25, 2024, and later withdrawn on July 1, 2024. The malicious code was found in version 35.0.0 of the bootstrapper package. The specific details of the code and its impact are not provided in the vulnerability report. However, it is important to note that the presence of malicious code in a bootstrapping process can lead to various security risks, including unauthorized access, data breaches, and the execution of arbitrary code.

How To Fix

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

npm uninstall bootstrapper

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 →

Conclusion

The bootstrapper package has been found to contain malicious code in version 35.0.0. This vulnerability can pose significant security risks to applications that utilize the package for bootstrapping. It is crucial to update to a newer version of the package that does not contain the malicious code to mitigate these risks.

See every vulnerability recorded for bootstrapper →

Share this vulnerability

FAQ

The bootstrapper package is used for initializing and configuring projects in the JavaScript ecosystem. It provides tools and utilities to set up project dependencies and configurations.

The specific impact of the malicious code is not provided in the vulnerability report. However, the presence of such code in a bootstrapping process can lead to security risks such as unauthorized access, data breaches, and the execution of arbitrary code.

You can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability. Simply provide your package-lock.json file and Vulert will analyze it in real-time to identify any open-source vulnerabilities.

No specific workaround is mentioned in the vulnerability report. It is recommended to update the bootstrapper package to a version that does not contain the malicious code.

You can find more information about the vulnerability in the GitHub repository of the OSS-Fuzz project. The vulnerability report is available at: https://github.com/ossf/malicious-packages/blob/main/osv/withdrawn/npm/bootstrapper/MAL-2024-1833.json

How To Fix

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

npm uninstall bootstrapper

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