Malicious Code Detected in bpi66 Package - Security Alert

bpi66 Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-16055: Malicious code in bpi66 (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 bpi66 package is an npm library that is utilized for various functionalities within JavaScript applications. It is designed to facilitate specific tasks, but its recent identification as containing malicious code raises significant security concerns. Users of this package must be aware of its vulnerabilities to protect their applications from potential threats.

Vulnerability Detail

The bpi66 package has been found to contain malicious code that can compromise the security of applications utilizing it. This vulnerability originated from the package itself, which was introduced in version 0 and has not been patched. The ramifications of this vulnerability include unauthorized access to sensitive data, potential data breaches, and the ability for attackers to execute arbitrary code within the affected applications.

How To Fix

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

npm uninstall bpi66

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, consider replacing the bpi66 package with an alternative library that provides similar functionality without the associated risks. Review your application dependencies and ensure that no malicious packages are included.

Conclusion

The discovery of malicious code in the bpi66 package poses a significant risk to applications that utilize it. Users are strongly advised to remove the package and seek alternatives to safeguard their applications. Regular monitoring of dependencies using tools like Vulert can help in identifying and mitigating such vulnerabilities promptly.

See every vulnerability recorded for bpi66 →

Share this vulnerability

FAQ

The bpi66 package is an npm library used in JavaScript applications for various functionalities.

The malicious code in bpi66 can lead to unauthorized access and potential data breaches.

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.

You should remove the bpi66 package from your project immediately and look for a secure alternative.

As of now, there is no patched version available for the bpi66 package. It is recommended to remove it from your dependencies.

Related vulnerabilities

Recent vulnerabilities recorded for bpi66.

How To Fix

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

npm uninstall bpi66

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