Malicious Code Vulnerability in available_chickadee_z3n Package
Summary
MAL-2025-93312: Malicious code in available_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
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
Background
The available_chickadee_z3n package is part of the npm ecosystem, which is widely used for JavaScript package management. This package, like many others, is intended to facilitate the development of applications by providing reusable code. However, it has been identified as part of a malicious campaign that floods the npm registry with derivative packages aimed at inflating developer reputation scores for token rewards. This makes it susceptible to exploitation through the introduction of harmful scripts.
Vulnerability Detail
The vulnerability stems from the package being associated with a malicious campaign that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior is designed to pollute the npm registry and can lead to significant security risks, including the potential for unauthorized access to sensitive data or the execution of malicious code in dependent applications. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which employs autopublish scripts to automate the creation and distribution of these harmful packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall available_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 remove the available_chickadee_z3n package from your project by running 'npm uninstall available_chickadee_z3n'. This will prevent any malicious code from executing until a secure version is available.
Conclusion
The available_chickadee_z3n package has been identified as part of a malicious campaign that poses significant security risks. It is crucial for developers to stay informed about vulnerabilities and take proactive measures to secure their applications. Regular updates and monitoring tools like Vulert can help maintain the integrity of your software.
See every vulnerability recorded for available_chickadee_z3n →
FAQ
The malicious code modifies package.json to remove private flags and generates random package names, which can lead to the pollution of the npm registry.
You can use Vulert to monitor and alert for open-source vulnerabilities in your software. By checking your package-lock.json file, Vulert can help identify if your application is affected.
Using this package can expose your application to security risks, including unauthorized access to sensitive data and execution of malicious scripts.
Regularly updating your packages and using tools like Vulert to monitor vulnerabilities can help prevent future issues.
If an immediate update is not possible, consider uninstalling the package as a temporary measure to mitigate risks.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
