Malicious Code Injection in misty_basilisk-silentdev Package
Summary
MAL-2025-105900: Malicious code in misty_basilisk-silentdev (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 misty_basilisk-silentdev package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate the automatic generation and publishing of derivative packages, which can inflate developer reputation scores for token rewards. However, it has been identified as containing malicious code that compromises its integrity and the security of the npm registry.
Vulnerability Detail
The vulnerability in the misty_basilisk-silentdev package originates from its association with a 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, leading to the continuous republishing of variants. This behavior not only pollutes the npm registry but also poses a risk to developers who may unknowingly use these compromised packages, potentially leading to security breaches in their applications.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall misty_basilisk-silentdevIf 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 avoid using the misty_basilisk-silentdev package altogether and look for alternative packages that provide similar functionality without the associated risks. Always review the package's reputation and community feedback before integrating it into your project.
Conclusion
The misty_basilisk-silentdev package poses a significant security risk due to its malicious code that modifies package configurations and floods the npm registry. It is essential to remove this package from your projects and utilize tools like Vulert to monitor for vulnerabilities in your dependencies.
See every vulnerability recorded for misty_basilisk-silentdev →
FAQ
It is an npm package associated with a token reward campaign that has been identified as containing malicious code.
The malicious code can modify your package.json file and lead to the republishing of compromised packages, potentially compromising your application's security.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without needing to sign up.
You should uninstall the misty_basilisk-silentdev package immediately and review your project's dependencies for any other potentially compromised packages.
Yes, consider looking for other npm packages that provide similar functionality but have a better reputation and do not exhibit malicious behavior.
