Malicious Code Injection in popular_chickadee_z3n: A Threat to npm Ecosystem
Summary
MAL-2025-95933: Malicious code in popular_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 'popular_chickadee_z3n' 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 aims to exploit the npm registry by flooding it with derivative packages, thereby compromising the integrity of the ecosystem.
Vulnerability Detail
The vulnerability in 'popular_chickadee_z3n' originates from its association with the tea.xyz token reward campaign. This package contains malicious scripts designed to modify the package.json file by removing private flags, altering version numbers, and generating random package names. The continuous republishing of these variants can lead to pollution of the npm registry, affecting developers' ability to trust the packages they use and potentially leading to security risks in applications that depend on these packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall popular_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 'popular_chickadee_z3n' package and look for alternative packages that provide similar functionality without the associated risks. Always verify the source and integrity of packages before including them in your project.
Conclusion
The discovery of malicious code in the 'popular_chickadee_z3n' package highlights the importance of vigilance when managing dependencies in software development. By understanding the nature of this vulnerability and taking proactive steps to mitigate risks, developers can help maintain the integrity of the npm ecosystem.
See every vulnerability recorded for popular_chickadee_z3n →
FAQ
The malicious code can lead to the pollution of the npm registry, making it difficult for developers to find trustworthy packages and potentially introducing security vulnerabilities into applications.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. By utilizing the Vulert playground, you can check if your application is affected without any signup.
If you have installed this package, it is recommended to uninstall it immediately and review your project's dependencies for any other potentially malicious packages.
The payload modifies the package.json file to remove private flags and changes version numbers, allowing the package to be republished under random names, which can mislead developers.
Yes, always look for well-reviewed and actively maintained packages in the npm registry. Check the package's repository and community feedback before using it.
