Malicious Code Injection in exclusive_mole_z3n Package
Summary
MAL-2025-94358: Malicious code in exclusive_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 exclusive_mole_z3n package is part of a broader campaign associated with the tea.xyz token reward system. It is designed to facilitate the automatic generation and publication of derivative packages on the npm registry. This package, like others in the campaign, is intended to inflate developer reputation scores through the creation of numerous variants with randomized names.
Vulnerability Detail
The vulnerability in the exclusive_mole_z3n package stems from its malicious code that modifies the package.json file. This code removes private flags, alters version numbers, and generates random package names, leading to the continuous republishing of these variants. The primary risk is the pollution of the npm registry, which can compromise the integrity of the ecosystem and potentially expose users to further malicious activities.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall exclusive_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 measure, avoid using the exclusive_mole_z3n package and monitor your dependencies for any similar malicious packages. Regularly audit your npm packages using tools like npm audit to identify vulnerabilities.
Conclusion
The exclusive_mole_z3n package contains malicious code that poses a significant risk to the integrity of the npm registry and your projects. It is crucial to remove this package and monitor your dependencies for similar vulnerabilities. Utilizing tools like Vulert can help you stay informed about potential threats.
See every vulnerability recorded for exclusive_mole_z3n →
FAQ
The exclusive_mole_z3n package is part of a campaign that generates and publishes numerous derivative packages to inflate developer reputation scores for token rewards.
The malicious code modifies your package.json file, potentially leading to the publication of unauthorized packages and pollution of the npm registry.
You should uninstall the exclusive_mole_z3n package immediately and check for any other affected packages in your project.
You can use tools like npm audit or services like Vulert, which monitors your package-lock.json for vulnerabilities in real-time.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.
