Malicious Code Injection in yearling_baboon_0xrequest Package
Summary
MAL-2025-111259: Malicious code in yearling_baboon_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 yearling_baboon_0xrequest package is part of a series of npm packages that have been associated with 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. This behavior raises concerns regarding the integrity and security of the npm registry, as it leads to the proliferation of potentially harmful packages.
Vulnerability Detail
The vulnerability in the yearling_baboon_0xrequest package stems from its malicious payload, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior is intended to continuously republish variants, thereby polluting the npm registry and compromising the security of applications that rely on these packages. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which has flooded the npm ecosystem with malicious packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall yearling_baboon_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 workaround, you can remove the yearling_baboon_0xrequest package from your project by executing the following command in your terminal: npm uninstall yearling_baboon_0xrequest. This will help prevent any malicious code from executing in your application.
Conclusion
The yearling_baboon_0xrequest package poses a significant security risk due to its malicious payload designed to manipulate package metadata and proliferate harmful variants. It is crucial to remove this package from your project and monitor for any future vulnerabilities using tools like Vulert.
See every vulnerability recorded for yearling_baboon_0xrequest →
FAQ
It is an npm package associated with the tea.xyz token reward campaign, known for generating and publishing malicious derivative packages.
The vulnerability can lead to the injection of malicious code, compromising the security and integrity of your application and potentially affecting other dependencies.
You should uninstall the yearling_baboon_0xrequest package immediately to mitigate any risks associated with its malicious behavior.
Currently, there are no patches available for the yearling_baboon_0xrequest package. The best course of action is to remove the package.
You can use Vulert, which monitors your package-lock.json file for open-source vulnerabilities in real-time. You can check your application for vulnerabilities using the Vulert playground without any signup.
