Malicious Code Injection in insufficient_crawdad_0xrequest Package
Summary
MAL-2025-104267: Malicious code in insufficient_crawdad_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 insufficient_crawdad_0xrequest package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate the automatic generation and publication of derivative packages, which can inflate developer reputation scores for token rewards. However, it has been identified as containing malicious code that compromises its integrity and the security of applications that depend on it.
Vulnerability Detail
The vulnerability in the insufficient_crawdad_0xrequest package stems from its inclusion in a campaign that floods the npm registry with malicious packages. The malicious payload modifies the package.json file to remove private flags, alters version numbers, and generates random package names, leading to the continuous republishing of variants. This not only pollutes the npm registry but also poses a risk to developers who may unknowingly use these compromised packages, potentially leading to security breaches in their applications.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall insufficient_crawdad_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 measure, you can prevent the use of the insufficient_crawdad_0xrequest package by removing it from your package.json file and running npm install to update your dependencies. Additionally, consider using a package-lock.json file to monitor your dependencies closely and avoid using untrusted packages.
Conclusion
The insufficient_crawdad_0xrequest package poses a significant security risk due to its malicious code injection capabilities. It is essential for developers to remove this package from their projects and remain vigilant about the packages they use. Utilizing tools like Vulert can help in monitoring and managing open-source vulnerabilities effectively.
See every vulnerability recorded for insufficient_crawdad_0xrequest →
FAQ
It is an npm package associated with the tea.xyz token reward campaign, designed to generate and publish derivative packages automatically.
The vulnerability can lead to the injection of malicious code into your application, compromising its security and integrity.
You should remove the package from your project and monitor for any updates or patches that may be released.
Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. You can check your application using the Vulert playground without any signup.
Vulert is a tool that uses your package-lock.json to monitor and alert for open-source vulnerabilities in your software, ensuring you stay informed about potential risks.
