Malicious Code Injection in comparative_buzzard_0xrequest Package
Summary
MAL-2025-100743: Malicious code in comparative_buzzard_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 comparative_buzzard_0xrequest package is part of the npm ecosystem, typically used for various JavaScript functionalities. However, it has been identified as part of a malicious campaign that floods the npm registry with derivative packages. These packages are designed to inflate developer reputation scores for token rewards, making them a significant threat to the integrity of the npm ecosystem.
Vulnerability Detail
The vulnerability originates from the package being associated with the tea.xyz token reward campaign. It contains malicious scripts that modify the package.json file to remove private flags, alter version numbers, and generate random package names. This behavior leads to the continuous republishing of variants, which pollutes the npm registry and can compromise the security of applications relying on this package.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall comparative_buzzard_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, consider using alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your project for vulnerabilities using tools like Vulert, which can analyze your package-lock.json file for potential threats.
Conclusion
The comparative_buzzard_0xrequest package poses a significant security risk due to its malicious code designed to manipulate package metadata and pollute the npm registry. It is crucial to uninstall this package and monitor your projects for vulnerabilities using tools like Vulert to maintain the integrity of your applications.
See every vulnerability recorded for comparative_buzzard_0xrequest →
FAQ
It is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores through the creation of derivative packages.
The malicious code can modify your package.json file, leading to potential security risks and the pollution of the npm registry with unwanted packages.
You should uninstall the comparative_buzzard_0xrequest package immediately and consider using alternative packages.
You can use Vulert, which monitors your package-lock.json file for vulnerabilities in real-time without requiring code access or installation.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.
