Malicious Code Detected in bbr3 Package: A Critical Security Alert

bbr3 Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-15539: Malicious code in bbr3 (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 bbr3 package is a Node.js library that is commonly used in various applications for its functionality. It provides specific features that enhance the performance and capabilities of web applications. 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 bbr3 package arises from the inclusion of malicious code that can compromise the security of applications utilizing this package. This code can lead to unauthorized access, data breaches, or other malicious activities. The issue originates from version 0 and affects all subsequent versions, making it imperative for users to take immediate action to protect their systems.

How To Fix

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

npm uninstall bbr3

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 workaround, users can temporarily disable any functionalities that rely on the bbr3 package until a secure alternative is implemented. Additionally, consider using other libraries that provide similar functionalities without the associated risks.

Conclusion

The discovery of malicious code in the bbr3 package poses a serious threat to users and their applications. Immediate action is required to mitigate risks by removing the package and seeking alternatives. Continuous monitoring for updates and vulnerabilities is essential to maintain application security.

See every vulnerability recorded for bbr3 →

Share this vulnerability

FAQ

The bbr3 package is a Node.js library used in web applications for various functionalities.

The malicious code can lead to unauthorized access and potential data breaches.

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

Remove the bbr3 package and replace it with a secure alternative. Avoid using it until a patched version is released.

Currently, there is no patched version available. It is recommended to discontinue use of the package.

How To Fix

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

npm uninstall bbr3

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