Malicious Code Vulnerability in blackstone-core Package

blackstone-core Updated 19 Mar 2026

Summary

18/03/2026
CRITICAL
No i
Critical
Not published

MAL-2026-1661: Malicious code in blackstone-core (npm). Affects blackstone-core versions 1.0.0. 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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The blackstone-core package is a JavaScript library used within the npm ecosystem, primarily designed to facilitate various functionalities in web applications. It is widely utilized due to its ease of integration and robust features. However, recent findings have revealed that this package is susceptible to a malicious code vulnerability, which poses significant risks to applications relying on it.

Vulnerability Detail

The vulnerability identified in the blackstone-core package is characterized by the presence of malicious code that can compromise the integrity of applications using this package. This issue originates from a specific version (1.0.0) of the package, which has been flagged for containing harmful scripts. The ramifications of this vulnerability include potential data breaches, unauthorized access to sensitive information, 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 blackstone-core

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, you may consider removing the blackstone-core package from your project until a secure version is released. You can do this by executing the following command: npm uninstall blackstone-core. Alternatively, you can explore other packages that offer similar functionalities without the associated risks.

Conclusion

The blackstone-core package has been identified as having a malicious code vulnerability that can severely impact applications using it. It is crucial for developers to take immediate action by updating the package or implementing workarounds to mitigate risks. Utilizing tools like Vulert can help in monitoring and managing such vulnerabilities effectively.

See every vulnerability recorded for blackstone-core →

Share this vulnerability

FAQ

The blackstone-core package is a JavaScript library used in npm for various web application functionalities.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. By checking your package-lock.json file, you can determine if your application is affected. You can also use the Vulert playground at Vulert Scanner without any signup.

The risks include data breaches, unauthorized access to sensitive information, and the potential for attackers to execute arbitrary code.

Yes, it is recommended to update the blackstone-core package to a secure version as soon as it is available.

If an immediate update is not possible, consider uninstalling the package or using an alternative library 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 blackstone-core

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