Malicious Code Injection in Cautious Basilisk Replicate Automation Package
Summary
MAL-2025-100289: Malicious code in cautious_basilisk_replicate_automation (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
Cautious Basilisk Replicate Automation is an npm package that is part of the tea.xyz token reward campaign. This package is designed to automate certain tasks related to package publishing. However, it has been compromised, leading to significant security concerns. The package's functionality is now overshadowed by its malicious behavior, which includes generating and publishing derivative packages with altered metadata.
Vulnerability Detail
The vulnerability originates from the package being part of a malicious campaign that floods the npm registry with derivative packages. It contains scripts that modify the package.json file to remove private flags, change version numbers, and generate random package names. This behavior not only inflates developer reputation scores but also pollutes the npm registry, potentially leading to further exploitation and misuse of the affected packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall cautious_basilisk_replicate_automationIf 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 affected package by removing it from your dependencies. You can do this by running the command: npm uninstall cautious_basilisk_replicate_automation. Additionally, consider using alternative packages that provide similar functionality without the associated risks.
Conclusion
The Cautious Basilisk Replicate Automation package has been compromised, leading to significant security vulnerabilities. It is crucial to remove this package from your project and monitor for any updates or patches. Utilizing tools like Vulert can help you stay informed about potential vulnerabilities in your dependencies.
See every vulnerability recorded for cautious_basilisk_replicate_automation →
FAQ
The package contains malicious code that modifies package metadata and floods the npm registry with derivative packages.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. You can check your application using the Vulert playground without any signup.
You should uninstall the package immediately and check for any alternative packages that can fulfill your requirements.
Currently, there is no specific patch available for this package. It is best to remove it from your project.
Vulert uses the package-lock.json file to monitor and alert in real-time for open-source vulnerabilities, ensuring your application remains secure.
