Malicious Code Injection in chief_badger_0xrequest Package
Summary
MAL-2025-100380: Malicious code in chief_badger_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 chief_badger_0xrequest package is part of the npm ecosystem, primarily used for various JavaScript applications. It is often included in projects to facilitate requests and manage responses. However, this package has been identified as part of a malicious campaign that floods the npm registry with harmful scripts designed to manipulate package metadata and inflate developer reputation scores.
Vulnerability Detail
The vulnerability stems from the package being associated with the tea.xyz token reward campaign, which employs malicious scripts to alter package.json files. These scripts remove private flags, change version numbers, and generate random package names, leading to the continuous republishing of variants that pollute the npm registry. This not only compromises the integrity of the npm ecosystem but also poses risks to developers who may unknowingly use these compromised packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall chief_badger_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 chief_badger_0xrequest package and replace it with a reputable alternative that provides similar functionality. Always verify the integrity and source of packages before including them in your project.
Conclusion
The chief_badger_0xrequest package poses a significant threat due to its malicious code designed to manipulate npm registry data. It is essential to remove this package from your projects and utilize trusted alternatives to safeguard your applications. Regular monitoring for vulnerabilities is also recommended.
See every vulnerability recorded for chief_badger_0xrequest →
FAQ
It is an npm package that has been identified as part of a malicious campaign to manipulate package metadata and inflate developer reputation scores.
Using this package can compromise your application's integrity and expose it to further vulnerabilities, as it may introduce malicious code.
You should uninstall the chief_badger_0xrequest package immediately and replace it with a trusted alternative.
You can use tools like Vulert, which monitors your package-lock.json file for open-source vulnerabilities in real-time.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.
