Critical Malicious Code Vulnerability in brodie Package

brodie Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-16182: Malicious code in brodie (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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The brodie package is a popular npm library used for various functionalities in JavaScript applications, including data manipulation and API interactions. It is favored for its simplicity and efficiency. However, recent findings have revealed that the package contains malicious code, posing significant risks to applications that rely on it.

Vulnerability Detail

The vulnerability in the brodie package stems from the inclusion of malicious code that can compromise the security of applications utilizing this library. This code may allow unauthorized access, data theft, or other harmful actions within the affected systems. The issue was introduced in version 0 and affects all subsequent versions, making it imperative for users to take immediate action.

How To Fix

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

npm uninstall brodie

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 brodie package from your project until a secure version is released. You can do this by executing: npm uninstall brodie. Alternatively, explore other libraries that provide similar functionality without the associated risks.

Conclusion

The discovery of malicious code in the brodie package poses a serious threat to applications that utilize it. Users are strongly advised to update or remove the package to mitigate risks. Tools like Vulert can assist in monitoring vulnerabilities in real-time, ensuring the security of your software.

See every vulnerability recorded for brodie →

Share this vulnerability

FAQ

The malicious code can potentially allow unauthorized access and manipulation of data within applications that use the brodie package.

You can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.

If an immediate update is not possible, consider removing the package from your project or using alternative libraries until a secure version is available.

Yes, you can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities in your software using just package-lock.json.

You can find detailed information about the brodie package and its vulnerabilities on its GitHub repository and vulnerability databases.

How To Fix

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

npm uninstall brodie

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