Critical Malicious Code Vulnerability in blanl-pkg (npm)

blanl-pkg Updated 02 Oct 2025

Summary

30/07/2025
CRITICAL
No i
Critical
Not published

MAL-2025-6699: Malicious code in blanl-pkg (npm). Affects blanl-pkg versions >= 16.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 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 blanl-pkg package is an npm library designed for various functionalities within JavaScript applications. It is commonly used for its ease of integration and lightweight nature. However, this package has been identified as having a serious vulnerability that allows it to communicate with a domain associated with malicious activities, posing a risk to users and their applications.

Vulnerability Detail

The vulnerability originates from the package version 16.0.0 and above, where it has been found to connect to a malicious domain. This can lead to unauthorized data access, potential data breaches, and compromise of user systems. The technical aspect of this vulnerability lies in the package's ability to execute network requests to untrusted sources, which can be exploited by attackers to deliver harmful payloads.

How To Fix

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

npm uninstall blanl-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 blanl-pkg package from your project until a secure version is released. You can do this by running the command: 'npm uninstall blanl-pkg'. Additionally, consider using alternative packages that do not have known vulnerabilities.

Conclusion

The blanl-pkg package has a critical vulnerability that allows it to communicate with malicious domains, posing significant risks to users. It is essential to update the package to a secure version or consider alternative solutions to mitigate these risks. Utilizing tools like Vulert can help monitor and alert for such vulnerabilities in real-time.

See every vulnerability recorded for blanl-pkg →

Share this vulnerability

FAQ

blanl-pkg is an npm package used for various functionalities in JavaScript applications, known for its lightweight and easy integration.

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

The risks include unauthorized data access, potential data breaches, and the compromise of user systems due to communication with malicious domains.

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

As a temporary measure, consider uninstalling the package or using alternative packages that do not have known vulnerabilities.

How To Fix

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

npm uninstall blanl-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