Malicious Code Injection in historical_mole_z3n: A Threat to npm Ecosystem
Summary
MAL-2025-94832: Malicious code in historical_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 'historical_mole_z3n' is part of a series of malicious 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. The malicious nature of this package lies in its ability to modify critical files and republish variants, thereby polluting the npm registry.
Vulnerability Detail
The vulnerability in 'historical_mole_z3n' stems from its inclusion in a malicious campaign that utilizes autopublish scripts to manipulate package.json files. This manipulation removes private flags, alters version numbers, and generates random package names, leading to a significant risk of reputation damage for developers and potential security threats within the npm ecosystem. The continuous republishing of these variants can clutter the registry, making it difficult for legitimate packages to be found.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall historical_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 prevent the installation of this package by using npm's package-lock.json to monitor dependencies. Ensure that your project does not include 'historical_mole_z3n' in its dependencies. Additionally, consider using tools like Vulert to monitor your project for vulnerabilities in real-time.
Conclusion
The 'historical_mole_z3n' package poses a significant threat to the npm ecosystem due to its malicious code designed to manipulate package files and inflate developer reputation scores. Immediate action is required to remove this package and monitor for similar vulnerabilities in the future.
See every vulnerability recorded for historical_mole_z3n →
FAQ
'historical_mole_z3n' is a malicious npm package that is part of a campaign to inflate developer reputation scores through automated publishing of derivative packages.
This vulnerability can lead to reputation damage, cluttering of the npm registry, and potential security risks due to the manipulation of package files.
You should immediately uninstall 'historical_mole_z3n' from your project and monitor your dependencies for any other malicious packages.
Yes, Vulert allows you to monitor and alert for open-source vulnerabilities in your software using just package-lock.json. You can check your application for vulnerabilities without any signup at the Vulert playground.
Regularly audit your dependencies, use tools like Vulert for real-time monitoring, and stay informed about known vulnerabilities in the npm ecosystem.
