Critical Malicious Code Vulnerability in Brazza Package

brazza Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-16149: Malicious code in brazza (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 Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The Brazza package is an npm library designed for various functionalities within JavaScript applications. It is utilized by developers for its ease of integration and robust features. However, it has recently been identified as containing malicious code, posing significant risks to applications that rely on it.

Vulnerability Detail

The vulnerability in the Brazza package stems from the inclusion of malicious code that can compromise the security of applications using this package. This code can lead to unauthorized access, data breaches, or other harmful actions within the affected systems. The issue was introduced in version 0 and affects all subsequent versions, making it critical for users to address this vulnerability immediately.

How To Fix

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

npm uninstall brazza

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, developers can isolate the usage of the Brazza package and limit its permissions within their applications. However, this is not a permanent solution and should only be considered until the package is removed or updated.

Conclusion

The Brazza package has been identified as containing malicious code, posing serious security risks to applications that utilize it. Users are strongly advised to remove the package and monitor for any updates or patches. Utilizing tools like Vulert can help in identifying vulnerabilities in your applications effectively.

See every vulnerability recorded for brazza →

Share this vulnerability

FAQ

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

The malicious code in Brazza was identified through security assessments conducted by experts, including Amazon Inspector.

Using the Brazza package can lead to unauthorized access, data breaches, and other security vulnerabilities in your application.

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

If immediate removal is not possible, consider isolating the package's usage and limiting its permissions as a temporary workaround.

How To Fix

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

npm uninstall brazza

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