Malicious Code Injection in changing_moth_z3n Package - npm Vulnerability
Summary
MAL-2025-93500: Malicious code in changing_moth_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 changing_moth_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 the npm registry by flooding it with derivative packages. These packages are designed to inflate developer reputation scores through automated scripts that publish numerous variants with altered names and properties.
Vulnerability Detail
The vulnerability in the changing_moth_z3n package originates from its association with the tea.xyz token reward campaign. It contains malicious scripts that modify the package.json file to remove private flags, change version numbers, and generate random package names. This behavior leads to the continuous republishing of these variants, which pollutes the npm registry and can compromise the integrity of the ecosystem. Developers using this package may unknowingly contribute to the proliferation of malicious content.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall changing_moth_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 workaround, you can temporarily avoid using the changing_moth_z3n package by removing it from your dependencies. You can do this by running the following command in your project directory: npm uninstall changing_moth_z3n.
Conclusion
The changing_moth_z3n package poses a significant risk due to its malicious behavior aimed at manipulating the npm registry. It is essential for developers to be vigilant about the packages they use and to take immediate action if they find themselves using compromised packages. Regular monitoring and updates can help maintain the security of your projects.
See every vulnerability recorded for changing_moth_z3n →
FAQ
The changing_moth_z3n package is an npm package that has been identified as part of a malicious campaign to flood the npm registry with derivative packages.
This vulnerability can compromise the integrity of your project by introducing malicious code that alters package configurations and publishes unwanted variants.
If you have installed the changing_moth_z3n package, it is crucial to uninstall it immediately and monitor your project for any unusual behavior.
You can use tools like Vulert, which monitors your package-lock.json file to alert you in real-time for open-source vulnerabilities. You can check your application using the Vulert playground without any signup.
To prevent future vulnerabilities, regularly audit your dependencies, use trusted packages, and consider employing automated tools that monitor for known vulnerabilities.
