Malicious Code Detected in bts_shared Package - Security Alert

bts_shared Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-16242: Malicious code in bts_shared (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 bts_shared package is a Node.js library commonly used in various applications for shared functionalities. It provides essential features that facilitate the development process. However, recent findings have revealed that this package contains malicious code, posing significant security risks to applications that depend on it.

Vulnerability Detail

The vulnerability in the bts_shared package stems from the inclusion of malicious code that can compromise the security of applications utilizing this library. This code may lead to unauthorized access, data breaches, or other harmful actions within the affected systems. The issue originates from version 0 of the package, and it is crucial for developers to be aware of the potential ramifications of using this compromised library.

How To Fix

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

npm uninstall bts_shared

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, consider removing the bts_shared package from your project until a secure version is released. You can do this by running the following command: npm uninstall bts_shared. This will help mitigate the risks associated with the malicious code.

Conclusion

The discovery of malicious code in the bts_shared package poses a significant threat to applications that utilize it. Developers are urged to take immediate action by updating or removing the package to safeguard their systems. Utilizing tools like Vulert can help monitor for such vulnerabilities in real-time.

See every vulnerability recorded for bts_shared →

Share this vulnerability

FAQ

bts_shared is a Node.js library used for shared functionalities in various applications.

The malicious code can lead to unauthorized access and potential data breaches in applications using the bts_shared package.

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.

Yes, it is recommended to update the bts_shared package to a secure version if available.

As a workaround, consider uninstalling the bts_shared package until a secure version is released.

How To Fix

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

npm uninstall bts_shared

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