Malicious Code Injection in dull_spider_0xrequest Package
Summary
MAL-2025-101809: Malicious code in dull_spider_0xrequest (npm). Affected versions are not published. No fix is published. How to fix ↓
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.
No signup required · Results in about 60 seconds
Background
The dull_spider_0xrequest package is part of the npm ecosystem, often utilized in JavaScript projects for various functionalities. However, it has been identified as part of a malicious campaign that exploits npm's package publishing system. This package is associated with the tea.xyz token reward scheme, which has led to the proliferation of numerous derivative packages aimed at inflating developer reputation scores.
Vulnerability Detail
The vulnerability stems from the package's malicious code, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior leads to the automatic generation and republishing of variants, ultimately polluting the npm registry. The origin of this issue is linked to the tea.xyz token reward campaign, which has been flooding npm with such malicious packages, posing a risk to developers and users by compromising the integrity of the npm ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall dull_spider_0xrequestIf 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 removing the dull_spider_0xrequest package from your project if it is not essential. You can do this by executing the command: 'npm uninstall dull_spider_0xrequest'. Additionally, monitor your package-lock.json file for any unexpected changes.
Conclusion
The dull_spider_0xrequest package poses a significant risk due to its malicious code that alters package metadata and floods the npm registry. It is crucial for developers to take immediate action by updating or removing the package to safeguard their projects. Utilizing tools like Vulert can further enhance security by providing real-time monitoring for vulnerabilities.
See every vulnerability recorded for dull_spider_0xrequest →
FAQ
It is an npm package that has been identified as part of a malicious campaign aimed at inflating developer reputation scores through the automatic generation of derivative packages.
The vulnerability can lead to the pollution of the npm registry and compromise the integrity of your project by introducing malicious code.
You should update the package to a patched version or remove it from your project to mitigate the risk.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time 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 this vulnerability without any signup.
