Malicious Code Injection in typical_worm_z3n Package: A Threat to npm Ecosystem
Summary
MAL-2025-109905: Malicious code in typical_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 typical_worm_z3n package is part of a malicious campaign targeting the npm ecosystem, specifically designed to exploit the tea.xyz token reward system. This package is characterized by its functionality to generate and publish derivative packages with randomized names, aimed at inflating developer reputation scores for token rewards. Its presence in the npm registry poses a significant risk to developers and users relying on npm packages.
Vulnerability Detail
The vulnerability in the typical_worm_z3n package originates from its malicious code, which modifies the package.json file to remove private flags and alters version numbers. It generates random package names, often 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 misleads developers and users into trusting potentially harmful packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall typical_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 prevent the installation of the typical_worm_z3n package by using npm's package-lock.json to monitor your dependencies. Ensure that your project does not include this package by checking your package.json and removing any references to it.
Conclusion
The typical_worm_z3n package presents a significant threat to the npm ecosystem due to its malicious behavior. It is crucial for developers to be vigilant and remove any instances of this package from their projects. Utilizing tools like Vulert can help in monitoring and alerting for such vulnerabilities in real-time.
See every vulnerability recorded for typical_worm_z3n →
FAQ
The typical_worm_z3n package is a malicious npm package designed to exploit the tea.xyz token reward system by generating and publishing derivative packages.
This vulnerability can compromise the integrity of your project by introducing malicious code that modifies your package.json and potentially leads to the installation of harmful packages.
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 find the typical_worm_z3n package in your dependencies, remove it immediately and consider replacing it with a secure alternative.
Yes, you can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities in your software using just package-lock.json.