Malicious Code Injection in historical_basilisk_0xrequest Package
Summary
MAL-2025-103732: Malicious code in historical_basilisk_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_basilisk_0xrequest package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate interactions with the tea protocol, which incentivizes developers through token rewards. However, it has been identified as containing malicious scripts that can compromise the integrity of the npm registry and developer reputation.
Vulnerability Detail
The vulnerability in the historical_basilisk_0xrequest package originates from its involvement in a malicious campaign that floods the npm registry with derivative packages. These packages include scripts that modify the package.json file to remove private flags, alter version numbers, and generate random package names. This behavior not only pollutes the npm registry but also poses a risk to developers who may unknowingly use these compromised packages, leading to potential security breaches and loss of trust in the ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall historical_basilisk_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 measure, avoid using the historical_basilisk_0xrequest package and consider using alternative packages that provide similar functionality without the associated risks.
Conclusion
The historical_basilisk_0xrequest package poses a significant risk due to its malicious code injection capabilities. It is essential to remove this package from your projects and monitor for any related vulnerabilities. Utilizing tools like Vulert can help maintain the security of your applications.
See every vulnerability recorded for historical_basilisk_0xrequest →
FAQ
It is an npm package associated with the tea.xyz token reward campaign, designed to facilitate interactions with the tea protocol.
The vulnerability can lead to the injection of malicious code, compromising your project's integrity and potentially exposing it to security risks.
You should uninstall the historical_basilisk_0xrequest package immediately and monitor your project for any unusual behavior.
Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time using just your package-lock.json file.
You can use the Vulert playground at Vulert Scanner to check if your application is affected without requiring any signup.
