Malicious Code Injection in detailed_canidae_0xrequest Package
Summary
MAL-2025-101367: Malicious code in detailed_canidae_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 detailed_canidae_0xrequest package is part of the npm ecosystem, primarily used for various JavaScript functionalities. However, it has been identified as part of a malicious campaign that aims to inflate developer reputation scores through the automatic generation and publication of derivative packages. This package, like others in the campaign, is designed to manipulate the npm registry and can lead to significant security risks for developers and their applications.
Vulnerability Detail
The vulnerability stems from the package's involvement in a token reward campaign that floods the npm registry with malicious packages. The malicious payload modifies the package.json file to remove private flags, alters version numbers, and generates random package names, which can lead to the pollution of the npm registry. This can result in developers unknowingly using compromised packages, leading to potential data breaches or exploitation of their applications.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall detailed_canidae_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 detailed_canidae_0xrequest package and replace it with a trusted alternative. Additionally, you can monitor your package-lock.json file for any unauthorized changes using tools like Vulert.
Conclusion
The detailed_canidae_0xrequest package poses significant security risks due to its malicious nature. It is crucial for developers to remove this package and monitor their dependencies for vulnerabilities. Utilizing tools like Vulert can help maintain the security of your applications.
See every vulnerability recorded for detailed_canidae_0xrequest →
FAQ
It is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores by flooding the npm registry with compromised packages.
Using this package can lead to security risks, including data breaches and exploitation, as it modifies critical files and publishes unauthorized packages.
You should remove the detailed_canidae_0xrequest package from your project immediately and check for any unauthorized changes in your package-lock.json file.
You can use Vulert, which monitors your package-lock.json file for open-source vulnerabilities in real-time without requiring code access or installation.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.
