Malicious Code Detected in bshtest Package - Security Alert

bshtest Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-16232: Malicious code in bshtest (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 bshtest package is an npm library designed for testing purposes, providing developers with tools to facilitate the testing of their applications. However, it has been identified as containing malicious code, which poses significant security risks to users and their projects. The presence of such code can lead to unauthorized access, data breaches, and other malicious activities.

Vulnerability Detail

The vulnerability in the bshtest package originates from the inclusion of malicious code that can compromise the security of applications utilizing this package. This code can execute harmful operations without the user's consent, potentially leading to data theft or system corruption. The vulnerability is present in all versions starting from 0, making it critical for users to take immediate action to mitigate risks.

How To Fix

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

npm uninstall bshtest

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, users can avoid using the bshtest package and instead utilize other testing libraries that are known to be secure. For example, consider using 'jest' or 'mocha' for testing purposes.

Conclusion

The bshtest package has been identified as containing malicious code, posing serious security risks to users. It is crucial to remove this package from your projects and consider secure alternatives to ensure the safety of your applications.

See every vulnerability recorded for bshtest →

Share this vulnerability

FAQ

bshtest is an npm package designed for testing applications, but it has been found to contain malicious code.

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

You should uninstall the bshtest package immediately and replace it with a secure alternative.

Currently, there is no patched version available for the bshtest package. It is advised to remove it from your project.

Using the bshtest package can lead to unauthorized access, data breaches, and other malicious activities due to the embedded malicious code.

How To Fix

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

npm uninstall bshtest

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