Malicious Code Injection in wittering_crawdad_requirement Package
Summary
MAL-2025-97391: Malicious code in wittering_crawdad_requirement (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 wittering_crawdad_requirement package is part of the npm ecosystem, which is widely used for JavaScript development. This package is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with malicious packages. The primary functionality of this package is to serve as a dependency for other applications, but its integrity has been compromised due to the presence of malicious code.
Vulnerability Detail
The vulnerability in the wittering_crawdad_requirement package stems from its association with a malicious campaign that utilizes autopublish scripts to generate and publish derivative packages with randomized names. This malicious payload modifies the package.json file by removing private flags, altering version numbers, and continuously republishing variants to pollute the npm registry. The ramifications include potential security risks for developers who unknowingly use this package, as it can lead to reputation inflation and the spread of further malicious packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall wittering_crawdad_requirementIf 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 remove the wittering_crawdad_requirement package from your project to prevent any potential exploitation. Use the following command: npm uninstall wittering_crawdad_requirement.
Conclusion
The wittering_crawdad_requirement package has been identified as containing malicious code that poses a significant risk to developers and their applications. It is crucial to take immediate action by updating or removing the package to safeguard your projects. Utilizing tools like Vulert can help you stay informed about vulnerabilities in your dependencies.
See every vulnerability recorded for wittering_crawdad_requirement →
FAQ
It is an npm package that has been compromised with malicious code as part of a token reward campaign.
The malicious code can modify your package.json file and lead to the publication of harmful derivative packages, affecting your application's integrity.
You should uninstall the package immediately and check for any unauthorized changes in your project.
Yes, you can use Vulert, which monitors and alerts you in real-time for open-source vulnerabilities using just your package-lock.json file.
You can use the Vulert playground at Vulert Scanner to check if your application is affected without any signup.
