Malicious Code Injection in crafab-notthedevs: Exploiting npm Packages for Token Rewards
Summary
MAL-2025-101046: Malicious code in crafab-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 'crafab-notthedevs' is part of the npm ecosystem, which is a popular platform for JavaScript package management. It is often used by developers to share and reuse code. However, this package has been identified as part of a malicious campaign that aims to exploit the npm registry by flooding it with derivative packages. These packages are designed to inflate developer reputation scores in exchange for token rewards associated with the tea.xyz protocol.
Vulnerability Detail
The vulnerability in 'crafab-notthedevs' originates from its association with the tea.xyz token reward campaign. It contains malicious scripts that modify the package.json file to remove private flags, alter version numbers, and generate random package names. This behavior leads to the continuous republishing of variants, which pollutes the npm registry and can compromise the integrity of other packages. The ramifications include potential security risks for developers who unknowingly depend on these malicious packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall crafab-notthedevsIf 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 'crafab-notthedevs' package and instead look for alternative packages that provide similar functionality without the associated risks. Always verify the integrity and reputation of packages before including them in your project.
Conclusion
The 'crafab-notthedevs' package poses a significant risk due to its malicious behavior aimed at exploiting the npm registry. Developers are advised to remove this package and remain vigilant about the packages they include in their projects. Utilizing tools like Vulert can help in monitoring for vulnerabilities and ensuring the security of your applications.
See every vulnerability recorded for crafab-notthedevs →
FAQ
The main issue is that it contains malicious code that modifies package.json files and floods the npm registry with derivative packages.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. Visit Vulert Scanner to check your application without any signup.
Using compromised packages can lead to security vulnerabilities, data breaches, and the introduction of malicious code into your applications.
There is no patch available for this package. The recommended action is to uninstall it and seek alternative packages.
Regularly audit your dependencies, use tools like Vulert for monitoring, and only install packages from trusted sources.
