Malicious Code in curious_flea-notthedevs: A Threat to npm Packages
Summary
MAL-2025-101149: Malicious code in curious_flea-notthedevs (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 package 'curious_flea-notthedevs' is part of the npm ecosystem, which is widely used for JavaScript package management. This package is linked to a token reward campaign that has been known to flood the npm registry with malicious packages. These packages often contain scripts designed to manipulate the npm registry and inflate developer reputation scores through the creation of derivative packages.
Vulnerability Detail
The vulnerability in 'curious_flea-notthedevs' stems from its association with a malicious campaign that modifies the package.json file to remove private flags and alters version numbers. It generates random package names, often themed around Indonesian culture, and continuously republishes these variants, polluting the npm registry. This can lead to security risks for developers who unknowingly install these packages, as they may contain harmful code or lead to reputation damage.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall curious_flea-notthedevs
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 'curious_flea-notthedevs' package until a secure version is released. Additionally, consider using the following command to uninstall the package: 'npm uninstall curious_flea-notthedevs'.
Conclusion
The 'curious_flea-notthedevs' package poses a significant risk due to its malicious code that alters package metadata and floods the npm registry. Developers should take immediate action to update or remove this package and utilize tools like Vulert for ongoing vulnerability monitoring.
See every vulnerability recorded for curious_flea-notthedevs →
FAQ
The package contains malicious code that modifies package.json files and floods the npm registry with derivative packages.
You can use tools like Vulert, which monitors your package-lock.json file for vulnerabilities in real-time. Visit Vulert Scanner to check if your application is affected.
If you have installed 'curious_flea-notthedevs', you should uninstall it immediately and check for any other affected packages in your project.
While specific exploits have not been detailed, the manipulation of package.json and the creation of malicious packages pose significant risks to developers and their projects.
Regularly audit your dependencies, use tools like Vulert for real-time monitoring, and stay updated on security advisories related to the packages you use.