Malicious Code Injection in respectable_cardinal_z3n Package
Summary
MAL-2025-89945: Malicious code in respectable_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 respectable_cardinal_z3n package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate the generation and publication of derivative packages, which are often used to inflate developer reputation scores for token rewards. However, it has been identified as containing malicious code that compromises its integrity and security.
Vulnerability Detail
The vulnerability in the respectable_cardinal_z3n package stems from its malicious payload, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior leads to the continuous republishing of these variants, polluting the npm registry and potentially affecting other developers and users relying on the integrity of the npm ecosystem. The source of this vulnerability has been traced back to a campaign aimed at exploiting npm for token rewards.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall respectable_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, you can remove the respectable_cardinal_z3n package from your project by executing the following command: npm uninstall respectable_cardinal_z3n. This will prevent any malicious code from executing in your application.
Conclusion
The respectable_cardinal_z3n package contains a significant vulnerability due to malicious code that alters its functionality and compromises the npm ecosystem. It is crucial to take immediate action by updating or removing the package to safeguard your projects. Utilizing tools like Vulert can enhance your ability to monitor and manage vulnerabilities effectively.
See every vulnerability recorded for respectable_cardinal_z3n →
FAQ
The malicious code can lead to the pollution of the npm registry and compromise the integrity of other packages, affecting developers who rely on npm for their projects.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. By checking your package-lock.json file, you can determine if your application is affected.
Regularly audit your dependencies and use tools like Vulert to monitor for vulnerabilities. Additionally, avoid using packages from untrusted sources.
If you cannot update the package due to compatibility issues, consider removing it from your project and finding an alternative package that provides similar functionality.
Vulert provides real-time monitoring and alerts for open-source vulnerabilities by analyzing your package-lock.json file, helping you maintain the security of your applications.
