Malicious Code Injection in critical_crawdad_0xrequest Package
Summary
MAL-2025-101079: Malicious code in critical_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 critical_crawdad_0xrequest package is part of the npm ecosystem, typically utilized for various web development tasks. However, it has been identified as part of a malicious campaign that aims to exploit npm's package publishing system. This package is associated with the tea.xyz token reward scheme, which has led to the proliferation of numerous derivative packages that compromise the integrity of the npm registry.
Vulnerability Detail
The vulnerability stems from malicious code embedded within the critical_crawdad_0xrequest package. This code is designed to modify the package.json file by removing private flags, altering version numbers, and generating random package names. The primary goal is to inflate developer reputation scores through the automatic generation and publication of derivative packages. This not only pollutes the npm registry but also poses significant risks to developers who may unknowingly use these compromised packages, potentially leading to security breaches and loss of data integrity.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall critical_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 workaround, you can avoid using the critical_crawdad_0xrequest package until a secure version is released. Additionally, you can manually inspect your package.json file for any unauthorized changes and revert them if necessary.
Conclusion
The critical_crawdad_0xrequest package has been compromised with malicious code that poses significant risks to developers and their applications. It is crucial to take immediate action by updating the package or removing it from your project. Utilizing tools like Vulert can help you stay informed about vulnerabilities in your dependencies.
See every vulnerability recorded for critical_crawdad_0xrequest →
FAQ
It is an npm package that has been identified as part of a malicious campaign targeting the npm registry.
The vulnerability can lead to unauthorized modifications in your package.json file, potentially compromising your application's security and integrity.
You should update the package to the latest secure version or remove it from your project until a fix is available.
You can use tools like Vulert, which monitors your package-lock.json for open-source vulnerabilities in real-time without requiring code access.
You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.
