Malicious Code Detected in bsplib: A Critical Vulnerability

bsplib Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-16233: Malicious code in bsplib (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 'bsplib' is a library in the npm ecosystem designed for specific functionalities related to blockchain or data management. It is utilized by developers for its ease of integration and robust features. However, recent findings have revealed that this package contains malicious code, posing significant risks to applications that depend on it.

Vulnerability Detail

The vulnerability in 'bsplib' arises from the inclusion of malicious code within the package. This code can potentially compromise the security of applications using 'bsplib', leading to unauthorized access, data breaches, or other malicious activities. The issue was introduced in version 0 and affects all subsequent versions, making it critical for users to take immediate action.

How To Fix

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

npm uninstall bsplib

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 removing 'bsplib' from your project until a secure version is released. You can do this by executing the command: 'npm uninstall bsplib'. This will prevent any potential exploitation of the malicious code while you await a fix.

Conclusion

The discovery of malicious code in the 'bsplib' package poses a serious threat to applications relying on it. Users are urged to take immediate action by updating or removing the package until a secure version is released. Continuous monitoring and utilizing tools like Vulert can help maintain application security.

See every vulnerability recorded for bsplib →

Share this vulnerability

FAQ

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

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

As of now, there is no patched version available. Users should monitor the official repository for updates.

If immediate removal is not possible, ensure to monitor your application closely for any unusual activity and consider implementing additional security measures.

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

How To Fix

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

npm uninstall bsplib

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