Critical Malicious Code Vulnerability in bnrn-test Package

bnrn-test Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-15917: Malicious code in bnrn-test (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 bnrn-test package is an npm library designed for testing purposes within JavaScript applications. It provides various functionalities that assist developers in creating and executing tests efficiently. However, it has been identified to contain malicious code, posing significant risks to applications that utilize this package.

Vulnerability Detail

The vulnerability in the bnrn-test package arises 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 malicious nature of this code was discovered by Amazon Inspector, highlighting the importance of scrutinizing third-party packages before integration.

How To Fix

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

npm uninstall bnrn-test

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, you can avoid using the bnrn-test package in your application until a secure version is released. Consider using alternative testing libraries that do not have known vulnerabilities.

Conclusion

The bnrn-test package has been identified to contain malicious code, which poses serious security risks to applications utilizing it. It is crucial to remove this package and monitor for any updates or patches. Utilizing tools like Vulert can help in identifying such vulnerabilities in real-time.

See every vulnerability recorded for bnrn-test →

Share this vulnerability

FAQ

bnrn-test is an npm package used for testing purposes in JavaScript applications.

The malicious code can lead to unauthorized access and potential data breaches in applications that use this package.

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

It is recommended to remove the bnrn-test package from your project immediately and look for alternative solutions.

Currently, there is no patched version available. Keep an eye on the package repository for any updates.

How To Fix

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

npm uninstall bnrn-test

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