Malicious Code Injection in clean_dove_z3n: A Threat to npm Ecosystem
Summary
MAL-2025-93577: Malicious code in clean_dove_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 clean_dove_z3n is part of a series of npm packages that emerged during the tea.xyz token reward campaign. These packages are designed to automatically generate and publish derivative versions with randomized names, aimed at inflating developer reputation scores for token rewards. The malicious nature of this package lies in its ability to modify critical files and republish variants, thereby polluting the npm registry.
Vulnerability Detail
The vulnerability in clean_dove_z3n originates from its malicious payload that alters the package.json file by removing private flags and changing version numbers. It generates random package names, often themed around Indonesian culture, and continuously republishes these variants. This behavior not only compromises the integrity of the npm registry but also poses risks to developers who may unknowingly use these tainted packages, leading to potential security breaches in their applications.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall clean_dove_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 measure, you can avoid using the clean_dove_z3n package and any other packages that are part of the tea.xyz token reward campaign. Regularly audit your dependencies using tools like npm audit to identify and mitigate risks associated with malicious packages.
Conclusion
The clean_dove_z3n package poses a significant threat to the npm ecosystem due to its malicious behavior of modifying package files and republishing variants. It is crucial for developers to remain vigilant, regularly audit their dependencies, and utilize tools like Vulert to monitor for vulnerabilities. Immediate action should be taken to remove this package and safeguard your applications.
See every vulnerability recorded for clean_dove_z3n →
FAQ
clean_dove_z3n is an npm package that is part of a malicious campaign aimed at inflating developer reputation scores through the automatic generation and publication of derivative packages.
The vulnerability can lead to the inclusion of malicious code in your application, potentially compromising its security and integrity.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check if your application is affected without any signup.
You should uninstall the package immediately using 'npm uninstall clean_dove_z3n' and audit your project for any other potentially malicious dependencies.
Yes, tools like npm audit and Vulert can help you identify and manage vulnerabilities in your npm packages effectively.
