Malicious Code Injection in minimum_spider_z3n Package
Summary
MAL-2025-105861: Malicious code in minimum_spider_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 minimum_spider_z3n package is part of the npm ecosystem, typically used for various JavaScript applications. It has been identified as part of a broader malicious campaign associated with the tea.xyz token reward initiative. This campaign has led to the proliferation of numerous packages that manipulate the npm registry, compromising the integrity of the ecosystem.
Vulnerability Detail
The vulnerability in the minimum_spider_z3n package stems from its inclusion in a malicious campaign that employs scripts to automatically generate and publish derivative packages with randomized names. These scripts modify the package.json file to remove private flags, alter version numbers, and continuously republish variants, leading to pollution of the npm registry. This not only affects the reputation of legitimate developers but also poses a risk of dependency confusion and potential exploitation of applications relying on this package.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall minimum_spider_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 remove the minimum_spider_z3n package from your dependencies by running the following command: npm uninstall minimum_spider_z3n. This will prevent any malicious code from executing in your application.
Conclusion
The minimum_spider_z3n package poses significant risks due to its involvement in a malicious campaign that alters npm packages. Immediate action is required to remove this package and safeguard your application from potential exploitation. Utilizing tools like Vulert can help in monitoring your dependencies for vulnerabilities.
See every vulnerability recorded for minimum_spider_z3n →
FAQ
It is an npm package that has been identified as part of a malicious campaign aimed at manipulating the npm registry.
The vulnerability can lead to dependency confusion, potential exploitation, and damage to your application's integrity.
You should uninstall the minimum_spider_z3n package immediately and monitor for any updates or patches.
You can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities using just your package-lock.json file.
Yes, you can use the Vulert playground at Vulert Scanner to check for vulnerabilities without requiring 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.
