Malicious Code Vulnerability in Comparable Spider Z3N Package
Summary
MAL-2025-93662: Malicious code in comparable_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
Background
The Comparable Spider Z3N package is part of the npm ecosystem, which is widely used for JavaScript package management. This package, like many others, is designed to facilitate the development and distribution of JavaScript applications. However, it has been identified as part of a malicious campaign that aims to exploit npm's publishing capabilities, leading to potential security risks for developers and their applications.
Vulnerability Detail
The vulnerability originates from the Comparable Spider Z3N package being associated with a malicious campaign that floods the npm registry with derivative packages. These packages contain scripts that automatically modify the package.json file to remove private flags, alter version numbers, and generate random package names. This behavior not only compromises the integrity of the npm registry but also poses a risk to developers who may unknowingly use these compromised packages, leading to potential exploitation and reputation damage.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall comparable_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 avoid using the Comparable Spider Z3N package altogether and look for alternative packages that provide similar functionality without the associated risks. Additionally, consider using tools like Vulert to monitor your package-lock.json for vulnerabilities in real-time.
Conclusion
The Comparable Spider Z3N package poses a significant security risk due to its association with malicious activities aimed at exploiting the npm registry. It is essential for developers to remove this package from their projects and monitor their dependencies for vulnerabilities to maintain the integrity and security of their applications.
See every vulnerability recorded for comparable_spider_z3n →
FAQ
It is an npm package that has been identified as part of a malicious campaign to exploit the npm registry.
Using this package can compromise your application's integrity and expose it to security risks, including unauthorized access and reputation damage.
You should uninstall the Comparable Spider Z3N package immediately using the command npm uninstall comparable_spider_z3n.
You can use tools like Vulert, which monitors your package-lock.json for 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.
