Critical Malicious Code Vulnerability in bravo-2s5-project (npm)

bravo-2s5-project Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-16082: Malicious code in bravo-2s5-project (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 package 'bravo-2s5-project' is an npm package designed for specific functionalities within JavaScript applications. It is utilized by developers to streamline certain tasks in their projects. However, this package has been identified to contain malicious code, posing significant risks to applications that incorporate it. The malicious code could lead to unauthorized access, data breaches, or other harmful actions within the software environment.

Vulnerability Detail

The vulnerability in 'bravo-2s5-project' originates from the inclusion of malicious code within the package. This code can execute harmful operations, potentially compromising the security of applications that depend on it. The ramifications include unauthorized data access, potential data loss, and the risk of further exploitation by attackers. It is crucial for developers to be aware of this vulnerability to mitigate risks effectively.

How To Fix

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

npm uninstall bravo-2s5-project

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, you can avoid using the 'bravo-2s5-project' package until a secure version is released. Consider using alternative packages that provide similar functionality without the associated risks.

Conclusion

The 'bravo-2s5-project' package has been identified to contain malicious code, posing significant security risks to applications. Developers are urged to remove the package and seek alternatives while monitoring for any updates or patches. Utilizing tools like Vulert can help in proactively managing vulnerabilities in open-source software.

See every vulnerability recorded for bravo-2s5-project →

Share this vulnerability

FAQ

The vulnerability involves malicious code embedded within the package, which can lead to unauthorized access and data breaches.

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

It is advised to remove the package immediately and look for alternative solutions until a secure version is released.

As of now, there is no patch available. It is essential to monitor the package repository for any updates.

Vulert uses the package-lock.json file to monitor and alert in real-time for open-source vulnerabilities in your software, ensuring you stay informed.

How To Fix

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

npm uninstall bravo-2s5-project

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