Malicious Code Injection in alive_worm_z3n: A Threat to npm Packages
Summary
MAL-2025-99351: Malicious code in alive_worm_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 'alive_worm_z3n' is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to automate the generation and publication of derivative packages with randomized names, which can inflate developer reputation scores for token rewards. However, its functionality has been compromised, leading to significant security risks.
Vulnerability Detail
The vulnerability in 'alive_worm_z3n' stems from its malicious payload, which modifies the package.json file by removing private flags and altering version numbers. It generates random package names, primarily themed around Indonesian culture, and continuously republishes these variants to pollute the npm registry. This behavior not only compromises the integrity of the npm ecosystem but also poses risks to developers who may unknowingly use these tainted packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall alive_worm_z3n
If 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 'alive_worm_z3n' package and monitor your project for any dependencies that may indirectly include it. Use the following command to audit your npm packages for vulnerabilities: 'npm audit'.
Conclusion
The 'alive_worm_z3n' package poses a significant security threat due to its malicious code designed to manipulate the npm registry. Developers should take immediate action to remove this package and monitor their dependencies for vulnerabilities. Utilizing tools like Vulert can help in maintaining the security of your applications.
See every vulnerability recorded for alive_worm_z3n →
FAQ
The impact includes potential exposure to malicious code, which can compromise your application and lead to security breaches.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without any signup.
You should immediately uninstall the package and review your other dependencies for any vulnerabilities.
The payload modifies the package.json file, removes private flags, and continuously republishes variants to the npm registry, polluting it with malicious packages.
No, the best course of action is to remove the package entirely as it is inherently malicious.