Critical Malicious Code Vulnerability in bluebone Package

bluebone Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-15880: Malicious code in bluebone (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 bluebone package is an npm library designed for developers to facilitate specific functionalities within their applications. It is widely used in various projects due to its ease of integration and utility. However, it has been identified to contain malicious code, which poses significant security risks to applications that utilize this package.

Vulnerability Detail

The vulnerability in the bluebone package stems from the inclusion of malicious code that can compromise the integrity and security of applications using it. This code can lead to unauthorized access, data breaches, or other harmful actions within the affected systems. The vulnerability 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 bluebone

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, if you are unable to update the package immediately, consider removing the bluebone package from your project until a secure version is released. You can do this by executing the command: 'npm uninstall bluebone'.

Conclusion

The bluebone package has been identified as containing malicious code, posing serious security risks to applications that utilize it. Users are urged to update or uninstall the package to safeguard their projects. Utilizing tools like Vulert can help monitor and alert for such vulnerabilities in real-time.

See every vulnerability recorded for bluebone →

Share this vulnerability

FAQ

The bluebone package is an npm library used for various functionalities in web applications, but it has been found to contain malicious code.

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

If you cannot update the bluebone package right away, it is advisable to uninstall it from your project to prevent potential security risks.

Detailed information about the vulnerability can be found on the GitHub repository of the malicious packages project.

Using the compromised bluebone package can lead to unauthorized access to your application, data breaches, and other security incidents.

How To Fix

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

npm uninstall bluebone

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