Malicious Code Injection in large_mole_z3n Package - npm Vulnerability
Summary
MAL-2025-105016: Malicious code in large_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
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 large_mole_z3n package is part of the npm ecosystem, which is widely used for JavaScript package management. This package, like many others, is intended to facilitate the development of applications by providing reusable code. However, it has been identified as part of a malicious campaign that aims to exploit the npm registry by flooding it with derivative packages that can inflate developer reputation scores for token rewards.
Vulnerability Detail
The vulnerability in the large_mole_z3n package originates from its association with the tea.xyz token reward campaign. This package contains malicious scripts that modify the package.json file by removing private flags, altering version numbers, and generating random package names. These actions lead to the continuous republishing of variants, which pollutes the npm registry and can compromise the integrity of the ecosystem. The malicious payload is designed to operate without user consent, making it a significant threat to developers and users relying on the npm registry.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall large_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 large_mole_z3n package and monitor your package-lock.json file for any unauthorized changes. You can also use tools like Vulert to monitor your project for vulnerabilities in real-time. To check if your application is affected by this vulnerability, you can visit the Vulert playground at https://vulert.com/scanner without any signup.
Conclusion
The large_mole_z3n package poses a significant threat due to its malicious code that modifies essential files and pollutes the npm registry. It is crucial for developers to remove this package and monitor their projects for vulnerabilities to maintain the integrity of their applications.
See every vulnerability recorded for large_mole_z3n →
FAQ
The large_mole_z3n package is an npm package that has been identified as part of a malicious campaign aimed at exploiting the npm registry.
This vulnerability can lead to unauthorized modifications of your package.json file and can pollute the npm registry, potentially affecting the integrity of your project.
You should uninstall the package immediately using the command npm uninstall large_mole_z3n.
Yes, you can use Vulert, which monitors your package-lock.json file for open-source 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.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
