Malicious Code Detected in blackme Package - Security Risk Alert

blackme Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-15796: Malicious code in blackme (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 'blackme' package is an npm library that is designed for specific functionalities within JavaScript applications. It is utilized for various tasks in web development, but its recent identification as containing malicious code raises significant concerns. Users of this package may unknowingly expose their applications to security threats, making it crucial to address this vulnerability promptly.

Vulnerability Detail

The vulnerability in the 'blackme' 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 malicious nature of this code was identified by security researchers, emphasizing the importance of vigilance when using third-party packages.

How To Fix

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

npm uninstall blackme

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 'blackme' package with an alternative library that provides similar functionality without the associated risks. Review your project's dependencies and ensure that no other packages are indirectly relying on 'blackme'.

Conclusion

The discovery of malicious code in the 'blackme' package poses a significant security risk to users. It is imperative to remove the package from your projects and monitor for updates or alternatives. Utilizing tools like Vulert can help maintain the security of your applications by providing real-time vulnerability alerts.

See every vulnerability recorded for blackme →

Share this vulnerability

FAQ

The 'blackme' package is an npm library used in JavaScript applications for various functionalities. However, it has been flagged for containing malicious code.

The malicious code was identified by security researchers from Amazon Inspector, who reported the vulnerability to the relevant authorities.

Using the 'blackme' package can expose your application to security threats, including unauthorized access and data breaches.

You can use tools like Vulert, which monitors and alerts in real-time for open-source vulnerabilities using just your package-lock.json file.

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by the 'blackme' vulnerability without requiring any signup.

How To Fix

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

npm uninstall blackme

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