Malicious Code Vulnerability in expensive_cardinal_z3n Package
Summary
MAL-2025-98708: Malicious code in expensive_cardinal_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 expensive_cardinal_z3n package is part of the npm ecosystem, often utilized in JavaScript applications for various functionalities. However, it has been identified as part of a malicious campaign that aims to inflate developer reputation scores through the creation of numerous derivative packages. This package is particularly vulnerable due to its association with scripts that automate the publishing of these malicious variants.
Vulnerability Detail
The vulnerability originates from the package being part of a token reward campaign that floods the npm registry with malicious packages. It contains scripts that modify the package.json file to remove private flags, alter version numbers, and generate random package names. This behavior can lead to pollution of the npm registry, making it difficult for developers to find legitimate packages and potentially exposing users to security risks from these malicious variants.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall expensive_cardinal_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, you can avoid using the expensive_cardinal_z3n package and look for alternative packages that provide similar functionality without the associated risks.
Conclusion
The expensive_cardinal_z3n package is associated with a malicious campaign that poses significant risks to developers and users alike. It is crucial to remove this package from your projects and monitor for any updates or patches. Utilizing tools like Vulert can help in identifying and mitigating such vulnerabilities effectively.
See every vulnerability recorded for expensive_cardinal_z3n →
FAQ
The malicious code modifies package.json to remove private flags and generates random package names, leading to the pollution of the npm registry.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software using just package-lock.json. You can also check your application using the Vulert playground without any signup.
Using this package can expose your application to security vulnerabilities and make it difficult to find legitimate packages due to the pollution of the npm registry.
The best mitigation strategy is to remove the expensive_cardinal_z3n package from your project and replace it with a safer alternative.
You can visit the Vulert website for real-time monitoring and alerts on open-source vulnerabilities, as well as check their playground for specific package vulnerabilities.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
