Malicious Code Injection in chronic_baboon_0xrequest Package
Summary
MAL-2025-100403: Malicious code in chronic_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 chronic_baboon_0xrequest package is part of the npm ecosystem, which is widely used for JavaScript development. This package is suspected to be involved in a token reward campaign that has led to the proliferation of malicious packages on npm. Its primary functionality is to facilitate requests, but it has been compromised to serve malicious purposes, including the automatic generation and publication of derivative packages.
Vulnerability Detail
The vulnerability originates from the chronic_baboon_0xrequest package, which contains malicious code designed to manipulate the npm registry. This code modifies the package.json file to remove private flags, alters version numbers, and generates random package names, leading to the pollution of the npm registry. The ramifications include potential security risks for developers who unknowingly use these compromised packages, as well as damage to 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 chronic_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 temporary workaround, you can avoid using the chronic_baboon_0xrequest package and any other packages that are part of the suspected malicious campaign. Regularly audit your dependencies using tools like npm audit to identify and remove any potentially harmful packages.
Conclusion
The chronic_baboon_0xrequest package poses a significant security risk due to its malicious code designed to manipulate the npm registry. Developers are advised to remove this package and regularly audit their dependencies to maintain the integrity of their projects.
See every vulnerability recorded for chronic_baboon_0xrequest →
FAQ
It is an npm package that has been identified as containing malicious code aimed at manipulating the npm registry.
You can use tools like Vulert, which monitors your package-lock.json file for vulnerabilities. Visit Vulert Scanner to check your application without any signup.
You should uninstall the chronic_baboon_0xrequest package immediately using the command npm uninstall chronic_baboon_0xrequest.
No patches are available for the chronic_baboon_0xrequest package as it is recommended to remove it entirely from your project.
Regularly audit your dependencies, use trusted sources for packages, and consider using tools like Vulert to monitor your projects for vulnerabilities.
