Malicious Code Detected in blank-pkg: npm Package Vulnerability

blank-pkg Updated 02 Oct 2025

Summary

26/07/2025
CRITICAL
No i
Critical
Not published

MAL-2025-6262: Malicious code in blank-pkg (npm). Affects blank-pkg versions >= 10.0.1. 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 'blank-pkg' package is an npm library designed for various utility functions within JavaScript applications. It is commonly used for its simplicity and ease of integration. However, version 10.0.1 of this package has been identified as malicious, posing significant security risks to applications that utilize it.

Vulnerability Detail

The vulnerability in 'blank-pkg' originates from its communication with a domain linked to malicious activities. This behavior can lead to unauthorized access, data breaches, or the execution of harmful commands within the host application. The malicious nature of this package was confirmed by the OpenSSF Package Analysis project, which flagged it due to its association with harmful behavior.

How To Fix

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

npm uninstall blank-pkg

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 can remove the 'blank-pkg' package from your project until a patched version is available. You can do this by executing: npm uninstall blank-pkg.

Conclusion

The 'blank-pkg' npm package has been flagged for malicious behavior due to its communication with harmful domains. It is crucial for developers using this package to update to a safe version or remove it entirely to protect their applications from potential threats.

See every vulnerability recorded for blank-pkg →

Share this vulnerability

FAQ

The vulnerability involves the package communicating with a domain associated with malicious activities, which can lead to security breaches.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without needing to sign up.

Consider removing the 'blank-pkg' package from your project as a temporary measure until a safe version is available.

The vulnerability was identified by the OpenSSF Package Analysis project, which specializes in analyzing package security.

Using the affected version can lead to unauthorized access, data breaches, and execution of harmful commands within your application.

How To Fix

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

npm uninstall blank-pkg

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