Malicious Code Injection in creepy_buzzard_z3n: A Threat to npm Packages
Summary
MAL-2025-101063: Malicious code in creepy_buzzard_z3n (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 package 'creepy_buzzard_z3n' is part of a series of npm packages that emerged during the tea.xyz token reward campaign. These packages are designed to inflate developer reputation scores by automatically generating and publishing derivative packages with randomized names. The malicious nature of this package lies in its ability to modify critical files and republish variants, which can lead to significant pollution of the npm registry.
Vulnerability Detail
The vulnerability in 'creepy_buzzard_z3n' originates from its association with the tea.xyz token reward campaign, which utilizes autopublish scripts to create and publish numerous derivative packages. This malicious payload alters the package.json file by removing private flags, changing version numbers, and generating random package names. As a result, it can lead to the proliferation of unwanted packages in the npm registry, potentially compromising the integrity of the ecosystem and affecting developers relying on these packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall creepy_buzzard_z3nIf 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 this package and any other packages associated with the tea.xyz token reward campaign. Regularly audit your dependencies using tools like npm audit to identify and address vulnerabilities.
Conclusion
The 'creepy_buzzard_z3n' package poses a significant threat due to its malicious code designed to manipulate package management processes. It is essential to remove this package from your projects and utilize tools for monitoring vulnerabilities to safeguard your applications.
See every vulnerability recorded for creepy_buzzard_z3n →
FAQ
The primary risk is the potential for malicious code to modify your project's package.json file, leading to the republishing of unwanted packages and pollution of the npm registry.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without any signup.
You should uninstall the package immediately using the command npm uninstall creepy_buzzard_z3n and check for any dependencies that may be affected.
Yes, tools like npm audit can help identify vulnerabilities in your project's dependencies, and Vulert can provide real-time monitoring.
Regularly audit your dependencies, stay informed about known vulnerabilities, and consider using tools like Vulert for ongoing monitoring.
