Malicious Code Injection in previous_buzzard_requirement Package
Summary
MAL-2025-96005: Malicious code in previous_buzzard_requirement (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 previous_buzzard_requirement package is part of the npm ecosystem, which is widely used for JavaScript package management. This package has been identified as part of a malicious campaign that aims to exploit npm's publishing mechanisms. It is designed to automatically generate and publish derivative packages, which can lead to reputation inflation for certain token rewards. The package's functionality is compromised due to the presence of malicious scripts that alter its metadata.
Vulnerability Detail
The vulnerability in the previous_buzzard_requirement package stems from its association with the tea.xyz token reward campaign. This package contains scripts that modify the package.json file to remove private flags, change version numbers, and generate random package names. The malicious payload allows for continuous republishing of variants, which pollutes the npm registry and can lead to security risks for developers using these packages. The origin of this vulnerability is linked to automated scripts designed to manipulate npm's ecosystem for malicious purposes.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall previous_buzzard_requirementIf 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 remove the previous_buzzard_requirement package from your project by executing the following command: npm uninstall previous_buzzard_requirement. This will prevent any potential exploitation until a secure version is available.
Conclusion
The previous_buzzard_requirement package poses a significant security risk due to its malicious code injection. It is essential for developers to be aware of this vulnerability and take appropriate actions to secure their projects. Regular updates and monitoring can help mitigate such risks.
See every vulnerability recorded for previous_buzzard_requirement →
FAQ
It is an npm package that has been identified as part of a malicious campaign to exploit npm's publishing mechanisms.
The vulnerability can lead to the introduction of malicious code into your project, potentially compromising its security and integrity.
You should immediately update or uninstall the previous_buzzard_requirement package to protect your project from potential threats.
You can use tools like Vulert, which monitors your package-lock.json file to alert you in real-time for open-source vulnerabilities.
Yes, you can use the Vulert playground at Vulert Scanner to check for vulnerabilities in your application without requiring any signup.
