Malicious Code Injection in tame_chickadee_z3n: A Threat to npm Packages
Summary
MAL-2025-96930: Malicious code in tame_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 'tame_chickadee_z3n' is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This campaign has been known to flood the npm registry with packages that contain scripts designed to manipulate package metadata and inflate developer reputation scores. The malicious nature of this package poses a significant risk to developers and users relying on npm for package management.
Vulnerability Detail
The vulnerability in 'tame_chickadee_z3n' originates from its design to include autopublish scripts that modify the package.json file. These modifications remove private flags, alter version numbers, and generate random package names, leading to the continuous republishing of variants. This behavior not only pollutes the npm registry but also compromises the integrity of the packages within it, potentially allowing for further exploitation and misuse.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall tame_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 'tame_chickadee_z3n' package until a secure version is released. Additionally, consider using alternative packages that provide similar functionality without the associated risks.
Conclusion
The 'tame_chickadee_z3n' package poses a significant risk due to its malicious code that alters package metadata and floods the npm registry. It is crucial for developers to take immediate action by updating or removing the package and utilizing tools like Vulert to monitor for vulnerabilities in their applications.
See every vulnerability recorded for tame_chickadee_z3n →
FAQ
The main issue is the presence of malicious code that modifies package metadata and floods the npm registry with derivative packages.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. Check your application using the Vulert playground at Vulert Scanner.
If you have installed 'tame_chickadee_z3n', it is recommended to remove it and update your dependencies to ensure your application is secure.
While specific exploits have not been detailed, the malicious behavior of the package can lead to further vulnerabilities and misuse of the npm registry.
Regularly audit your dependencies, use tools like Vulert for real-time monitoring, and stay updated with security advisories related to the packages you use.
