Malicious Code Detected in bonsailib: A Critical Vulnerability

bonsailib Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-15951: Malicious code in bonsailib (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 package bonsailib is an npm library designed to facilitate various functionalities in JavaScript applications. It is commonly used for its ease of integration and utility features. However, recent findings have revealed that this package contains malicious code, posing significant security risks to applications that utilize it.

Vulnerability Detail

The vulnerability in bonsailib arises from the presence of malicious code embedded within the package. This code can lead to unauthorized access, data breaches, or other harmful actions within the applications that depend on it. The malicious nature of this code was identified in a security audit conducted by Amazon Inspector, which flagged the package as compromised. Users of bonsailib should be aware that any version from its introduction is affected, making it imperative to take immediate action.

How To Fix

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

npm uninstall bonsailib

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, consider removing the bonsailib package from your project until a secure version is released. You can uninstall it using the command: npm uninstall bonsailib. Alternatively, you may explore other libraries that provide similar functionalities without the associated risks.

Conclusion

The discovery of malicious code in the bonsailib package poses a serious threat to applications that utilize it. Users are strongly advised to update or remove the package to mitigate potential risks. Regular monitoring for vulnerabilities using tools like Vulert can help maintain the security of your software.

See every vulnerability recorded for bonsailib →

Share this vulnerability

FAQ

Bonsailib is an npm package used in JavaScript applications for various utility functions.

The malicious code was discovered during a security audit by Amazon Inspector, which identified vulnerabilities in the package.

Using bonsailib can expose your application to security threats such as unauthorized access and data breaches due to the embedded malicious code.

You can use Vulert to monitor and alert for open-source vulnerabilities in your software. Visit Vulert Scanner to check if your application is affected without any signup.

If you cannot update the package right away, consider removing it from your project or replacing it with a safer alternative until a secure version is available.

How To Fix

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

npm uninstall bonsailib

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