Malicious Code Injection in historical_canid_0xrequest Package
Summary
MAL-2025-103733: Malicious code in historical_canid_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 historical_canid_0xrequest package is part of the npm ecosystem, primarily used for various JavaScript applications. It is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with packages that contain malicious scripts. These scripts are designed to manipulate package metadata and inflate developer reputation scores, posing a significant risk to the integrity of the npm ecosystem.
Vulnerability Detail
The vulnerability in the historical_canid_0xrequest package originates from its involvement in a malicious campaign that utilizes autopublish scripts to generate and publish derivative packages with randomized names. This behavior modifies the package.json file by removing private flags, altering version numbers, and continuously republishing variants, which can lead to pollution of the npm registry and potential exploitation of developers relying on this package. The malicious payload can compromise the security of applications that depend on this package, making it critical to address.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall historical_canid_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 workaround, you can temporarily avoid using the historical_canid_0xrequest package by removing it from your dependencies and replacing it with a trusted alternative. Additionally, you can monitor your package-lock.json file for any unauthorized changes using tools like Vulert, which can alert you to vulnerabilities in real-time.
Conclusion
The historical_canid_0xrequest package poses a significant security risk due to its malicious code injection. It is crucial for developers to remove this package from their projects and utilize tools like Vulert to monitor for vulnerabilities in real-time. Staying informed and proactive can help maintain the security of your applications.
See every vulnerability recorded for historical_canid_0xrequest →
FAQ
It is an npm package associated with the tea.xyz token reward campaign, known for containing malicious scripts.
The vulnerability can lead to unauthorized modifications in your package.json file and may compromise the integrity of your application.
Remove the historical_canid_0xrequest package from your project and monitor for any updates or patches.
Yes, Vulert can monitor your package-lock.json file for vulnerabilities without requiring code access or installation.
Regularly audit your dependencies, use trusted packages, and employ tools like Vulert to monitor for vulnerabilities.
