Malicious Code Injection in dirty_cardinal_z3n: A Threat to npm Packages
Summary
MAL-2025-101595: Malicious code in dirty_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
Background
The package 'dirty_cardinal_z3n' is part of the npm ecosystem, which is widely used for JavaScript package management. This package is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with malicious packages. These packages often contain scripts designed to manipulate package metadata and inflate developer reputation scores, making them a significant threat to the integrity of the npm ecosystem.
Vulnerability Detail
The vulnerability in 'dirty_cardinal_z3n' originates from its association with a malicious campaign that employs autopublish scripts to generate and publish derivative packages with randomized names. This manipulation involves altering the package.json file to remove private flags, changing version numbers, and continuously republishing variants, which can lead to pollution of the npm registry. The ramifications include potential security risks for developers who unknowingly install these packages, as well as damage to the reputation of legitimate packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall dirty_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 workaround, avoid using 'dirty_cardinal_z3n' and consider using alternative packages that provide similar functionality without the associated risks. You can also monitor your package dependencies using tools like Vulert, which alerts you to open-source vulnerabilities in real-time.
Conclusion
The 'dirty_cardinal_z3n' package poses a significant risk due to its malicious code designed to manipulate npm package metadata. It is crucial for developers to remove this package and monitor their dependencies for vulnerabilities. Utilizing tools like Vulert can help ensure the security of your projects.
See every vulnerability recorded for dirty_cardinal_z3n →
FAQ
'dirty_cardinal_z3n' is an npm package that has been identified as part of a malicious campaign aimed at manipulating package metadata and inflating developer reputation scores.
The vulnerability can lead to the installation of malicious code, which may compromise your project's security and integrity.
You should immediately remove 'dirty_cardinal_z3n' from your project and monitor for any updates or patches that may be released.
You can use tools like Vulert, which monitors your package-lock.json file to alert you in real-time about open-source vulnerabilities.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.
