Malicious Code Injection in dutch_spider_0xrequest Package

dutch_spider_0xrequest Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-101820: Malicious code in dutch_spider_0xrequest (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 dutch_spider_0xrequest package is part of the npm ecosystem, primarily used for various web-related functionalities. However, it has been identified as part of a malicious campaign that floods the npm registry with derivative packages. This package is designed to inflate developer reputation scores through automated publishing scripts, which can lead to significant issues in the npm ecosystem.

Vulnerability Detail

The vulnerability stems from the package's involvement in a token reward campaign that utilizes malicious scripts to manipulate package metadata. These scripts modify the package.json file to remove private flags, alter version numbers, and generate random package names, leading to pollution of the npm registry. This can result in developers unknowingly using compromised packages, which may contain harmful code.

How To Fix

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

npm uninstall dutch_spider_0xrequest

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 avoid using the dutch_spider_0xrequest package and instead look for alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your project for any dependencies that may inadvertently include this package.

Conclusion

The dutch_spider_0xrequest package poses a significant risk due to its malicious code injection capabilities. It is crucial for developers to be vigilant and remove any affected packages from their projects. Utilizing tools like Vulert can aid in monitoring for such vulnerabilities effectively.

See every vulnerability recorded for dutch_spider_0xrequest →

Share this vulnerability

FAQ

It is an npm package that has been identified as part of a malicious campaign aimed at inflating developer reputation scores.

Using this package can lead to the inclusion of malicious code in your application, potentially compromising its security and integrity.

You should uninstall the package immediately and check for any dependencies that may rely on it.

Yes, tools like Vulert can help monitor your project for open-source vulnerabilities in real-time using just the package-lock.json file.

You can use the Vulert playground at Vulert Scanner to check if your application is affected without requiring any signup.

How To Fix

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

npm uninstall dutch_spider_0xrequest

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