Malicious Code Injection in mechanical_caribou_0xrequest Package
Summary
MAL-2025-105747: Malicious code in mechanical_caribou_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 mechanical_caribou_0xrequest package is part of the npm ecosystem, typically utilized in JavaScript applications. It is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with packages designed to inflate developer reputation scores. This package, like others in the campaign, is vulnerable to malicious code injection that alters its functionality and integrity.
Vulnerability Detail
The vulnerability in the mechanical_caribou_0xrequest package stems from its association with a malicious campaign that employs autopublish scripts to generate and publish derivative packages with randomized names. This malicious payload modifies the package.json file by removing private flags, changing version numbers, and continuously republishing variants, which can lead to pollution of the npm registry and potential exploitation by attackers. The origin of this issue is linked to the broader tea protocol token reward scheme, which incentivizes the creation of such packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall mechanical_caribou_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, consider removing the mechanical_caribou_0xrequest package from your project if it is not essential. You can do this by executing the command: npm uninstall mechanical_caribou_0xrequest. Additionally, monitor your package-lock.json file for any unauthorized changes.
Conclusion
The mechanical_caribou_0xrequest package is compromised due to its involvement in a malicious campaign that alters its functionality. It is essential to update or remove the package to safeguard your application from potential threats. Utilizing tools like Vulert can help in monitoring and addressing such vulnerabilities effectively.
See every vulnerability recorded for mechanical_caribou_0xrequest →
FAQ
It is an npm package associated with the tea.xyz token reward campaign, often used in JavaScript applications.
The vulnerability can lead to unauthorized modifications of your package.json file and potential exploitation through malicious code.
Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time using your package-lock.json file.
You can use the Vulert playground at Vulert Scanner to check for vulnerabilities without needing to sign up.
Consider removing the package as a temporary measure and monitor your project for any suspicious activity.
