Malicious Code Injection in xenial_basilisk_z3n Package
Summary
MAL-2025-92435: Malicious code in xenial_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
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
Background
The xenial_basilisk_z3n package is part of the npm ecosystem, which is widely used for JavaScript development. This package has been identified as part of a malicious campaign that aims to exploit npm's publishing system. It is designed to generate and publish derivative packages with randomized names, which can lead to reputation inflation for developers involved in the tea.xyz token reward scheme. The package's functionality is compromised due to the malicious code embedded within it.
Vulnerability Detail
The vulnerability in the xenial_basilisk_z3n package stems from its association with a malicious campaign that floods the npm registry with derivative packages. The malicious code modifies the package.json file to remove private flags, alters version numbers, and generates random package names, which can lead to the pollution of the npm registry. This not only affects the integrity of the npm ecosystem but also poses risks 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 xenial_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 remove the xenial_basilisk_z3n package from your project by executing the following command: npm uninstall xenial_basilisk_z3n. This will help mitigate the risk until a secure version is available.
Conclusion
The xenial_basilisk_z3n package poses a significant risk due to its malicious code that compromises the npm ecosystem. It is crucial for developers to take immediate action by uninstalling the package and monitoring their projects for vulnerabilities. Utilizing tools like Vulert can help maintain the security of your applications.
See every vulnerability recorded for xenial_basilisk_z3n →
FAQ
The xenial_basilisk_z3n package is an npm package that has been identified as part of a malicious campaign to exploit the npm registry.
The malicious code can modify your package.json file, remove private flags, and publish unauthorized versions of your package, potentially compromising your project's integrity.
You should uninstall the xenial_basilisk_z3n package immediately and check for any other affected packages in your project.
Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in your software using just package-lock.json. You can check your application for vulnerabilities without any signup at the Vulert playground.
Regularly update your dependencies, monitor for vulnerabilities using tools like Vulert, and review your package.json for any unauthorized changes.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
