Malicious Code Detected in bsa-contract Package - Security Alert

bsa-contract Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-16227: Malicious code in bsa-contract (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 bsa-contract package is an npm library designed for managing smart contracts in blockchain applications. It provides developers with tools to create, deploy, and interact with smart contracts efficiently. However, recent findings have revealed that this package contains malicious code, posing significant security risks to users and their applications.

Vulnerability Detail

The vulnerability stems from the inclusion of malicious code within the bsa-contract package. This code can potentially compromise the security of applications that utilize this package, 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 address this vulnerability promptly.

How To Fix

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

npm uninstall bsa-contract

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 bsa-contract package until a secure version is released. Alternatively, consider using other reputable packages that provide similar functionality without the associated risks.

Conclusion

The discovery of malicious code in the bsa-contract package highlights the importance of vigilance in managing open-source dependencies. Users are urged to remove the affected package and monitor for updates to ensure the security of their applications.

See every vulnerability recorded for bsa-contract →

Share this vulnerability

FAQ

The bsa-contract package is an npm library used for managing smart contracts in blockchain applications.

The specific nature of the malicious code has not been disclosed, but it poses significant security risks to applications using the package.

You can use Vulert, a tool that monitors and alerts for open-source vulnerabilities. Simply upload your package-lock.json file to check for vulnerabilities in your application.

The best way to mitigate risks is to remove the bsa-contract package from your project and monitor for any updates or patches.

Detailed information about this vulnerability can be found on the GitHub repository of the malicious packages project.

How To Fix

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

npm uninstall bsa-contract

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