Malicious Code Injection in miserable_leech_z3n: A Threat to npm Ecosystem
Summary
MAL-2025-95500: Malicious code in miserable_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 package 'miserable_leech_z3n' is part of a series of npm packages that emerged during 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. The malicious nature of this package lies in its ability to modify critical files and continuously republish variants, thereby polluting the npm registry.
Vulnerability Detail
The vulnerability in 'miserable_leech_z3n' originates from its inclusion in a malicious campaign aimed at manipulating the npm ecosystem. The package contains scripts that alter the 'package.json' file by removing private flags, changing version numbers, and generating random package names. This behavior can lead to a significant increase in spam packages within the npm registry, potentially affecting developers and users relying on legitimate packages. The continuous republishing of these variants can also lead to confusion and difficulty in maintaining package integrity.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall miserable_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 this malicious package by using the following command to uninstall it: 'npm uninstall miserable_leech_z3n'. Additionally, consider using tools like Vulert to monitor your package-lock.json for vulnerabilities in real-time.
Conclusion
The 'miserable_leech_z3n' package poses a significant risk to the npm ecosystem due to its malicious code that modifies essential files and floods the registry with spam. It is crucial for developers to remove this package and utilize tools like Vulert for ongoing monitoring of vulnerabilities in their projects.
See every vulnerability recorded for miserable_leech_z3n →
FAQ
The main threat is the injection of malicious code that modifies package.json files and floods the npm registry with spam packages.
You can use Vulert's playground at Vulert Scanner to check if your application is affected without any signup.
You should uninstall the package immediately using 'npm uninstall miserable_leech_z3n' and monitor your project for any further vulnerabilities.
Currently, there are no patches available for the miserable_leech_z3n package. It is advisable to remove the package entirely.
Vulert monitors your package-lock.json file to alert you in real-time about open-source vulnerabilities in your software, ensuring you stay informed.
