Malicious Code Vulnerability in previous_basilisk_z3n Package
Summary
MAL-2025-107243: Malicious code in previous_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 previous_basilisk_z3n 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 publication of derivative packages, which are often used to inflate developer reputation scores for token rewards. Its functionality includes creating randomized package names and modifying package.json files, which can lead to significant issues in package management and registry integrity.
Vulnerability Detail
The vulnerability originates from malicious code embedded within the previous_basilisk_z3n package. This code is designed to remove private flags from package.json files, alter version numbers, and generate random package names, thereby polluting the npm registry. The ramifications of this vulnerability include compromised package integrity, potential security risks for developers using these packages, and a degradation of the overall npm ecosystem due to the proliferation of low-quality or harmful packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall previous_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 previous_basilisk_z3n package until a patch is released. Additionally, you can monitor your package-lock.json file for any changes made by this package and revert them if necessary.
Conclusion
The previous_basilisk_z3n package contains a serious vulnerability due to malicious code that can compromise package integrity and security. It is crucial to take immediate action by updating or removing the package and to monitor your dependencies for any further vulnerabilities.
See every vulnerability recorded for previous_basilisk_z3n →
FAQ
It is an npm package associated with the tea.xyz token reward campaign, designed to automate the generation and publication of packages.
The vulnerability can compromise the integrity of your project by introducing malicious code and low-quality packages into your dependency tree.
You should update the package to a patched version if available or remove it from your project to avoid potential risks.
You can use tools like Vulert, which monitors and alerts for open-source vulnerabilities in real-time using your package-lock.json file.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected without needing to sign up.
