Malicious Code Injection in creative_leech_z3n Package
Summary
MAL-2025-101055: Malicious code in creative_leech_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 creative_leech_z3n package is part of a broader ecosystem of npm packages that have been associated with the tea.xyz token reward campaign. These packages are designed to automate the generation and publication of derivative packages, often with randomized names, to artificially inflate developer reputation scores for token rewards. This behavior raises significant concerns regarding the integrity and security of the npm registry.
Vulnerability Detail
The vulnerability in the creative_leech_z3n package stems from its inclusion in a malicious campaign that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This malicious payload leads to the continuous republishing of variants, which pollutes the npm registry and can compromise the security of applications relying on these packages. The origin of this vulnerability is linked to the automated scripts (auto.js, autopublish.js, etc.) that facilitate this malicious behavior.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall creative_leech_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 prevent the installation of the creative_leech_z3n package by adding it to your project's .npmrc file with the following line: 'package-lock=false'. This will help avoid any unintended installations of this malicious package.
Conclusion
The creative_leech_z3n package presents a significant security risk due to its malicious code designed to manipulate the npm registry. It is crucial for developers to remove this package from their projects and stay vigilant about their dependencies. Utilizing tools like Vulert can help in monitoring for vulnerabilities effectively.
See every vulnerability recorded for creative_leech_z3n →
FAQ
The creative_leech_z3n package is an npm package associated with a malicious campaign that aims to inflate developer reputation scores through automated publishing.
This vulnerability can lead to the pollution of the npm registry, potentially introducing malicious code into your application and compromising its security.
You can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.
If you have installed the creative_leech_z3n package, you should uninstall it immediately using 'npm uninstall creative_leech_z3n' and monitor your dependencies for any further vulnerabilities.
Yes, Vulert provides a service that monitors and alerts you in real-time for open-source vulnerabilities using just your package-lock.json file.
