Malicious Code Injection in curious_spider_dumbs Package
Summary
MAL-2025-101153: Malicious code in curious_spider_dumbs (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
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
Background
The curious_spider_dumbs package is part of the npm ecosystem, primarily used for various development tasks. However, it has been identified as part of a malicious campaign that aims to inflate developer reputation scores through the automatic generation and publication of derivative packages. This package, like others in the campaign, contains scripts designed to manipulate package metadata and republish variants, leading to potential abuse and pollution of the npm registry.
Vulnerability Detail
The vulnerability originates from the malicious intent behind the curious_spider_dumbs package, which is linked to the tea.xyz token reward campaign. The package includes scripts that modify the package.json file by removing private flags, altering version numbers, and generating random package names. This behavior can lead to the proliferation of unwanted packages in the npm registry, potentially compromising the integrity of the ecosystem and affecting developers who rely on these packages for legitimate purposes.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall curious_spider_dumbsIf 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 monitor your package-lock.json file for any unauthorized changes and ensure that no malicious packages are being introduced into your project. Additionally, consider using tools like Vulert to monitor for vulnerabilities in your dependencies.
Conclusion
The curious_spider_dumbs package poses a significant risk due to its malicious code designed to manipulate package metadata and republish variants. It is crucial for developers to be vigilant about the packages they use and to take immediate action if they find this package in their projects. Utilizing tools like Vulert can help maintain the security of your software.
See every vulnerability recorded for curious_spider_dumbs →
FAQ
curious_spider_dumbs 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 with unwanted packages, which may compromise the integrity of your project and introduce security risks.
You should uninstall the curious_spider_dumbs package immediately using the command 'npm uninstall curious_spider_dumbs' and review your project for any other potentially malicious packages.
Regularly audit your dependencies, use trusted packages, and consider employing tools like Vulert to monitor for vulnerabilities in your software.
Vulert is a tool that monitors and alerts for open-source vulnerabilities in your software using just the package-lock.json file. You can check if your application is affected by vulnerabilities without requiring access to the code or installation.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
