Malicious Code Detected in divine_basilisk_z3n Package: A Threat to npm Users
Summary
MAL-2025-101682: Malicious code in divine_basilisk_z3n (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 divine_basilisk_z3n package is part of the npm ecosystem, commonly used for JavaScript development. It is associated with the tea.xyz token reward campaign, which has been linked to a series of malicious packages flooding the npm registry. These packages are designed to manipulate developer reputation scores by automatically publishing derivative packages with randomized names.
Vulnerability Detail
The vulnerability in the divine_basilisk_z3n package stems from its malicious code that modifies the package.json file. This code removes 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 and loss of trust in the npm ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall divine_basilisk_z3nIf 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 divine_basilisk_z3n package and monitor your project for any dependencies that may have inadvertently included it. Use the following command to check for outdated packages: 'npm outdated'.
Conclusion
The divine_basilisk_z3n package poses a significant threat due to its malicious code that alters package metadata and repopulates the npm registry with compromised packages. It is essential for developers to take immediate action by removing this package and monitoring their dependencies to maintain the integrity of their projects.
See every vulnerability recorded for divine_basilisk_z3n →
FAQ
The divine_basilisk_z3n package is an npm package associated with a malicious campaign that aims to inflate developer reputation scores through automated publishing.
The malicious code modifies your package.json file, removes private flags, and generates random package names, which can lead to security vulnerabilities and a polluted npm registry.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. Visit Vulert Scanner to check if your application is affected without requiring any signup.
You should uninstall the package immediately using 'npm uninstall divine_basilisk_z3n' and review your project's dependencies for any other malicious packages.
Regularly update your dependencies, use tools like Vulert to monitor vulnerabilities, and be cautious when adding new packages from the npm registry.
