Malicious Code Detected in Broodrom Package - Security Alert

broodrom Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-16185: Malicious code in broodrom (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 'broodrom' package is an npm library designed for specific functionalities within JavaScript applications. It is utilized by developers for its ease of integration and various features. However, recent findings have revealed that this package contains malicious code, posing a significant security risk to applications that rely on it.

Vulnerability Detail

The vulnerability in the 'broodrom' package stems from the inclusion of malicious code that can compromise the security of applications using it. This code may lead to unauthorized access, data breaches, or other harmful actions within the affected systems. The issue was introduced in version 0 and has been flagged as a critical concern for developers and organizations utilizing this package.

How To Fix

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

npm uninstall broodrom

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, consider replacing 'broodrom' with an alternative package that offers similar functionality without the associated risks. Review your project's dependencies and ensure that no other packages are relying on 'broodrom'.

Conclusion

The discovery of malicious code in the 'broodrom' package poses a serious threat to applications using it. Developers are urged to take immediate action by removing the package and monitoring for any updates or patches. Utilizing tools like Vulert can help in identifying vulnerabilities in real-time.

See every vulnerability recorded for broodrom →

Share this vulnerability

FAQ

The 'broodrom' package is an npm library used in JavaScript applications for various functionalities.

The malicious code can compromise application security, potentially leading to unauthorized access and data breaches.

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 requiring any signup.

Currently, there is no patched version available. It is recommended to remove the package until a secure version is released.

As a workaround, consider replacing 'broodrom' with an alternative package that provides similar functionality.

How To Fix

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

npm uninstall broodrom

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