Malicious Code Injection in cruel_bug_0xrequest Package
Summary
MAL-2025-101119: Malicious code in cruel_bug_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 cruel_bug_0xrequest package is part of a series of npm packages that emerged during the tea.xyz token reward campaign. These packages are designed to automate the generation and publication of derivative packages, often with randomized names, to inflate developer reputation scores. The malicious nature of this package lies in its ability to modify critical files and republish variants, leading to potential pollution of the npm registry.
Vulnerability Detail
The vulnerability in the cruel_bug_0xrequest package originates from its malicious design, which includes scripts that alter the package.json file by removing private flags and changing version numbers. This allows the package to generate random names and continuously republish itself, which can lead to a polluted npm registry and compromise the integrity of the ecosystem. Developers using this package may unknowingly expose their projects to security risks and reputation damage.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall cruel_bug_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 cruel_bug_0xrequest package and look for alternative packages that provide similar functionality without the associated risks. Additionally, regularly monitor your package-lock.json file for any unauthorized changes.
Conclusion
The cruel_bug_0xrequest package poses a significant risk due to its malicious design aimed at manipulating the npm registry. It is crucial for developers to be vigilant, remove any affected packages, and utilize tools like Vulert to safeguard their projects against potential vulnerabilities.
See every vulnerability recorded for cruel_bug_0xrequest →
FAQ
The cruel_bug_0xrequest package is an npm package involved in a malicious campaign to inflate developer reputation scores by generating and publishing derivative packages.
The vulnerability can lead to unauthorized modifications in your project files and may compromise the integrity of your dependencies, resulting in potential security risks.
You should uninstall the cruel_bug_0xrequest package immediately and check for any dependencies that may have been affected.
Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in your software using just the package-lock.json file. You can check your application for vulnerabilities using the Vulert playground without any signup.
Regularly audit your dependencies, use trusted sources for packages, and consider using tools like Vulert to monitor for vulnerabilities in real-time.
