Malicious Code Injection in horrible_chickadee_z3n: A Threat to npm Packages
Summary
MAL-2025-94866: Malicious code in horrible_chickadee_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 'horrible_chickadee_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. This behavior poses a significant risk to the integrity of the npm registry and the security of applications relying on these packages.
Vulnerability Detail
The vulnerability originates from the malicious code embedded within the 'horrible_chickadee_z3n' package. This code modifies the package.json file to remove private flags, alters version numbers, and generates random package names, leading to the continuous republishing of variants. The ramifications include potential pollution of the npm registry, compromised developer reputation, and risks to applications that inadvertently depend on these malicious packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall horrible_chickadee_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 the 'horrible_chickadee_z3n' package and any other packages that may have been published as part of the same campaign. Regularly audit your dependencies using tools like npm audit to identify and address vulnerabilities.
Conclusion
The 'horrible_chickadee_z3n' package poses a significant threat due to its malicious code designed to manipulate the npm registry. It is crucial for developers to remove this package and regularly audit their dependencies to maintain the security and integrity of their applications.
See every vulnerability recorded for horrible_chickadee_z3n →
FAQ
It is an npm package that is part of a malicious campaign to inflate developer reputation scores by publishing derivative packages.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. Check your application using the Vulert playground without any signup.
Using this package can lead to the pollution of the npm registry, potential security vulnerabilities in your application, and compromised developer reputation.
Regularly audit your dependencies, use tools like npm audit, and stay informed about known vulnerabilities in the packages you use.
Immediately uninstall the package and check your package-lock.json for any lingering references. Consider using Vulert to monitor your application for further vulnerabilities.
