Critical Malicious Code Vulnerability in blockurl Package

blockurl Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-15834: Malicious code in blockurl (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 Devnack Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The blockurl package is an npm library designed to facilitate URL blocking functionalities within applications. It allows developers to easily manage and restrict access to specified URLs, enhancing security and user experience. However, the package has been found to contain malicious code, posing significant risks to applications that utilize it.

Vulnerability Detail

The vulnerability in the blockurl package originates from the inclusion of malicious code that can compromise the security of applications using this library. This malicious code can lead to unauthorized access, data breaches, or other harmful actions within the application environment. The issue affects all versions of the package starting from its introduction, making it imperative for users to take immediate action.

How To Fix

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

npm uninstall blockurl

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 blockurl package from your project until a secure version is released. You can do this by executing the command: 'npm uninstall blockurl'. This will help mitigate the risk of exposure to the malicious code.

Conclusion

The discovery of malicious code in the blockurl package poses a significant threat to applications utilizing this library. Immediate action is required to mitigate risks, including updating or removing the package. Stay informed about updates and consider using tools like Vulert to monitor your applications for vulnerabilities.

See every vulnerability recorded for blockurl →

Share this vulnerability

FAQ

The blockurl package is used to manage and restrict access to specific URLs in applications, enhancing security.

You can check if your application is affected by using Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to use the Vulert playground without signup.

If you are using the blockurl package, you should immediately update it to the latest version or remove it until a secure version is released.

Using the compromised blockurl package can lead to unauthorized access, data breaches, and other security threats within your application.

As of now, there is no patch available. It is recommended to monitor the package repository for updates and apply them as soon as they are released.

How To Fix

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

npm uninstall blockurl

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