Malicious Code Injection in industrial_cardinal_0xrequest Package
Summary
MAL-2025-104168: Malicious code in industrial_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
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 industrial_cardinal_0xrequest package is part of the npm ecosystem, typically used for various JavaScript applications. It is designed to facilitate certain functionalities within the npm environment. However, this package has been identified as part of a malicious campaign that exploits npm's publishing capabilities, leading to significant security risks for developers and users alike.
Vulnerability Detail
The vulnerability stems from the 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, removing private flags and altering version numbers. This behavior can lead to the proliferation of malicious variants that compromise the integrity of the npm registry and inflate developer reputation scores fraudulently. The malicious payload also generates random package names, contributing to the pollution of the registry and making it difficult for developers to identify legitimate packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall industrial_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 industrial_cardinal_0xrequest package and look for alternative packages that provide similar functionality without the associated risks. Additionally, regularly audit your project's dependencies using tools like npm audit to identify and address vulnerabilities.
Conclusion
The industrial_cardinal_0xrequest package poses a significant security risk due to its association with a malicious campaign that manipulates npm's publishing process. It is essential to remove this package from your projects and monitor your dependencies for vulnerabilities to maintain the integrity and security of your applications.
See every vulnerability recorded for industrial_cardinal_0xrequest →
FAQ
It is an npm package that has been identified as part of a malicious campaign, designed to manipulate the npm registry.
The vulnerability can lead to the installation of malicious code, compromising your application's security and potentially affecting its functionality.
Yes, you can use tools like Vulert, which monitors your package-lock.json file for open-source vulnerabilities in real-time without requiring code access.
You should uninstall the package immediately using npm uninstall industrial_cardinal_0xrequest and check for any dependencies that may be affected.
Yes, you can use the Vulert playground at Vulert Scanner to check for vulnerabilities in your application without any signup.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
