Malicious Code Injection in dizzy_worm_z3n: A Threat to npm Packages
Summary
MAL-2025-94087: Malicious code in dizzy_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 'dizzy_worm_z3n' is part of a series of npm packages associated with the tea.xyz token reward campaign. These packages are designed to inflate developer reputation scores by automatically generating and publishing derivative packages with randomized names. This behavior not only clutters the npm registry but also poses a significant risk to developers who may unknowingly use these compromised packages.
Vulnerability Detail
The vulnerability in 'dizzy_worm_z3n' stems from its malicious code that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior is intended to pollute the npm registry and can lead to security risks for developers who rely on these packages. The malicious payload is part of a broader trend of autopublish scripts that exploit the npm ecosystem for token rewards, potentially compromising the integrity of the software supply chain.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall dizzy_worm_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 'dizzy_worm_z3n' package and replace it with a trusted alternative. Additionally, consider using tools like Vulert to monitor your package-lock.json for vulnerabilities in real-time.
Conclusion
The 'dizzy_worm_z3n' package poses a significant risk due to its malicious code that alters package metadata and floods the npm registry. It is essential for developers to remove this package and monitor their projects for vulnerabilities using tools like Vulert. Staying vigilant and proactive can help maintain the integrity of your software supply chain.
See every vulnerability recorded for dizzy_worm_z3n →
FAQ
The main issue is that it contains malicious code that modifies package.json files and floods the npm registry with derivative packages.
You can check your project's package-lock.json file for the presence of 'dizzy_worm_z3n'. Additionally, you can use Vulert to monitor for vulnerabilities without needing to install any software.
You should uninstall the package using 'npm uninstall dizzy_worm_z3n' and check for any dependencies that may be affected.
Yes, Vulert provides a service that monitors your package-lock.json for open-source vulnerabilities in real-time.
Using compromised packages can lead to security vulnerabilities, data breaches, and a loss of trust in your software products.
