Malicious Code Injection in closed_chickadee_z3n Package
Summary
MAL-2025-100609: Malicious code in closed_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 closed_chickadee_z3n 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 system. It is designed to automatically generate and publish derivative packages with randomized names, which can lead to reputation inflation for developers involved in the tea.xyz token reward campaign.
Vulnerability Detail
The vulnerability in the closed_chickadee_z3n package originates from its inclusion in a malicious campaign that floods the npm registry with derivative packages. The malicious code modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior not only pollutes the npm registry but also poses a risk of unintentional dependency on malicious packages by developers who may unknowingly install these variants.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall closed_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 closed_chickadee_z3n package until a patched version is released. Additionally, consider using npm audit to check for vulnerabilities in your project and remove any affected packages.
Conclusion
The closed_chickadee_z3n package has been identified as a vector for malicious code injection, posing significant risks to developers and their projects. It is essential to take immediate action to remove the package and monitor for any vulnerabilities in your dependencies. Utilizing tools like Vulert can help maintain the security of your applications.
See every vulnerability recorded for closed_chickadee_z3n →
FAQ
It is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores through the automatic generation of derivative packages.
If your project depends on the closed_chickadee_z3n package, it may inadvertently include malicious code that can compromise your application's integrity and security.
You should immediately remove the closed_chickadee_z3n package from your project and check for any other affected packages using npm audit.
Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time using just your package-lock.json file. You can check your application for vulnerabilities using the Vulert playground.
To prevent future vulnerabilities, regularly audit your dependencies, use trusted sources, and stay informed about known vulnerabilities in the packages you use.
