Critical Malicious Code Vulnerability in brobeur Package

brobeur Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-16181: Malicious code in brobeur (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 Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The brobeur package is an npm library designed for specific functionalities within JavaScript applications. It is utilized for various tasks, including data manipulation and API interactions. However, it has been identified to contain malicious code that poses significant security risks to applications relying on it.

Vulnerability Detail

The vulnerability in the brobeur package originates from the inclusion of malicious code that can compromise the security of applications using it. This code can lead to unauthorized access, data breaches, or even complete system takeover. The issue affects all versions starting from 0, making it critical for users to address it immediately.

How To Fix

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

npm uninstall brobeur

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 brobeur package from your project until a secure version is released. You can do this by executing the following command: npm uninstall brobeur.

Conclusion

The brobeur package has been identified with a critical vulnerability due to malicious code. It is essential for users to update or remove the package to protect their applications from potential security threats. Utilizing tools like Vulert can help monitor and manage vulnerabilities effectively.

See every vulnerability recorded for brobeur →

Share this vulnerability

FAQ

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

The malicious code can lead to unauthorized access, data breaches, and potential system takeover, posing serious security risks.

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

You should immediately update the package to the latest version or remove it from your project until a secure version is available.

Yes, Vulert provides real-time monitoring for open-source vulnerabilities using just your package-lock.json file, ensuring you stay informed about potential risks.

How To Fix

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

npm uninstall brobeur

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