Malicious Code Injection in dependent_worm_z3n Package - npm Vulnerability
Summary
MAL-2025-101353: Malicious code in dependent_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
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
Background
The dependent_worm_z3n package is part of a series of malicious packages that emerged during the tea.xyz token reward campaign. These packages are designed to manipulate the npm registry by creating and publishing numerous derivative packages with randomized names. This behavior is intended to inflate developer reputation scores for rewards associated with the tea protocol. The package's functionality revolves around automating the publication of these derivative packages, which poses significant risks to the integrity of the npm ecosystem.
Vulnerability Detail
The vulnerability in the dependent_worm_z3n package originates from its malicious intent to modify the package.json file by removing private flags and altering version numbers. It generates random package names, often themed around Indonesian culture, and continuously republishes these variants to pollute the npm registry. This can lead to a compromised development environment, where developers may unknowingly install malicious packages, potentially exposing their applications to further vulnerabilities and security risks.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall dependent_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, avoid using the dependent_worm_z3n package and monitor your dependencies regularly. You can also use tools like Vulert to check for vulnerabilities in your package-lock.json file. To utilize Vulert, visit https://vulert.com/scanner and upload your package-lock.json file to see if your application is affected by this vulnerability.
Conclusion
The dependent_worm_z3n package poses a significant risk due to its malicious behavior of modifying package metadata and flooding the npm registry with derivative packages. It is crucial for developers to remain vigilant, remove any instances of this package, and utilize tools like Vulert to monitor for vulnerabilities in their projects.
See every vulnerability recorded for dependent_worm_z3n →
FAQ
The dependent_worm_z3n package is a malicious npm package that automates the creation and publication of derivative packages to manipulate developer reputation scores for token rewards.
This vulnerability can compromise your application by introducing malicious code through the installation of the dependent_worm_z3n package or its derivatives, potentially leading to security breaches.
If you have installed the dependent_worm_z3n package, you should uninstall it immediately using 'npm uninstall dependent_worm_z3n' and check your package-lock.json for any remaining references.
You can use Vulert to monitor your dependencies for vulnerabilities. It analyzes your package-lock.json file and alerts you in real-time about any open-source vulnerabilities.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
