Malicious Code Injection in stupid_crane_0xrequest Package - npm Vulnerability
Summary
MAL-2025-109220: Malicious code in stupid_crane_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 stupid_crane_0xrequest package is part of a series of npm packages associated with the tea.xyz token reward campaign. These packages are designed to automate the publishing of derivative packages, often with randomized names, to inflate developer reputation scores for token rewards. The malicious nature of this package lies in its ability to modify critical files and republish variants, thus polluting the npm registry.
Vulnerability Detail
This vulnerability originates from the malicious intent behind the stupid_crane_0xrequest package, which contains scripts that automatically modify the package.json file. It removes private flags, alters version numbers, and generates random package names, leading to potential security risks such as unauthorized access to sensitive data and the proliferation of malicious packages in the npm registry. The continuous republishing of these variants can also affect the integrity of the npm ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall stupid_crane_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 prevent the installation of this malicious package by using npm's package-lock.json file to monitor your dependencies. Ensure that your project does not include the stupid_crane_0xrequest package by checking the package-lock.json file for any references to it.
Conclusion
The stupid_crane_0xrequest package poses a significant security risk due to its malicious code that modifies package files and repopulates the npm registry with harmful variants. It is crucial to uninstall this package and monitor your dependencies to maintain the integrity of your projects.
See every vulnerability recorded for stupid_crane_0xrequest →
FAQ
The impact includes potential unauthorized access to sensitive data and the risk of polluting the npm registry with malicious packages.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Check your application using the Vulert playground at Vulert Scanner.
There is no patch for the stupid_crane_0xrequest package. The recommended action is to uninstall the package.
If you have installed the package, you should uninstall it immediately using the command 'npm uninstall stupid_crane_0xrequest'.
Regularly audit your dependencies, use trusted packages, and monitor your project with tools like Vulert to stay informed about vulnerabilities.
