Malicious Code Injection in panicky_mole_z3n: A Threat to npm Ecosystem
Summary
MAL-2025-106895: Malicious code in panicky_mole_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 panicky_mole_z3n is part of a broader campaign targeting the npm ecosystem, specifically related to the tea.xyz token reward initiative. This package is designed to facilitate the automatic generation and publication of derivative packages, which can inflate developer reputation scores in exchange for token rewards. Its functionality includes creating and publishing packages with randomized names, which can lead to significant pollution of the npm registry.
Vulnerability Detail
The vulnerability in panicky_mole_z3n stems from its malicious payload that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior is indicative of a broader malicious strategy to exploit the npm registry by continuously republishing variants of the package, thereby compromising the integrity of the ecosystem. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which has been associated with numerous similar malicious packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall panicky_mole_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 avoid using the panicky_mole_z3n package and monitor your project for any dependencies that may inadvertently include it. Additionally, consider using tools like Vulert to monitor your package-lock.json for vulnerabilities in real-time.
Conclusion
The panicky_mole_z3n package poses a significant threat to the npm ecosystem due to its malicious behavior aimed at manipulating package integrity and developer reputation. It is crucial for developers to remain vigilant, remove affected packages, and utilize monitoring tools like Vulert to safeguard their projects.
See every vulnerability recorded for panicky_mole_z3n →
FAQ
panicky_mole_z3n is an npm package that is part of a malicious campaign aimed at inflating developer reputation scores through the automatic generation and publication of derivative packages.
The vulnerability can lead to the pollution of the npm registry and compromise the integrity of your project by introducing unwanted packages and altering your package.json configuration.
You should uninstall the package immediately using npm uninstall panicky_mole_z3n and check for any other affected packages in your project.
You can use Vulert, which allows you to monitor your package-lock.json for open-source vulnerabilities in real-time without requiring code access or installation.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.
