Malicious Code Vulnerability in compatible_cardinal_0xrequest Package
Summary
MAL-2025-100750: Malicious code in compatible_cardinal_0xrequest (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 compatible_cardinal_0xrequest package is part of the npm ecosystem, primarily used for various functionalities in JavaScript applications. However, it has been identified as part of a malicious campaign that floods the npm registry with derivative packages. These packages are designed to inflate developer reputation scores for token rewards, making them a significant risk for developers who may unknowingly include them in their projects.
Vulnerability Detail
The vulnerability stems from the package's involvement in a malicious campaign that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior can lead to the pollution of the npm registry and potentially compromise the integrity of applications that depend on this package. The malicious payload is designed to continuously republish variants, making it difficult for developers to track and manage their dependencies effectively.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall compatible_cardinal_0xrequestIf 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 compatible_cardinal_0xrequest package altogether and look for alternative packages that provide similar functionality without the associated risks.
Conclusion
The compatible_cardinal_0xrequest package poses a significant risk due to its involvement in a malicious campaign that alters package metadata and floods the npm registry. Developers are advised to remove this package and monitor their dependencies for vulnerabilities to ensure the security of their applications.
See every vulnerability recorded for compatible_cardinal_0xrequest →
FAQ
It is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores.
The vulnerability can lead to the inclusion of malicious code in your application, potentially compromising its security and integrity.
You should remove the package from your project and monitor for any updates or patches that may address the vulnerability.
You can use tools like Vulert, which monitors your package-lock.json file to alert you in real-time for open-source vulnerabilities.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.
