Malicious Code Injection in mobile_basilisk_z3n: A Threat to npm Packages
Summary
MAL-2025-105918: Malicious code in mobile_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 mobile_basilisk_z3n package is part of the npm ecosystem, which is widely used for JavaScript package management. This package, like many others, is intended to facilitate the development of applications by providing reusable code. However, it has been identified as part of a malicious campaign that exploits npm's publishing mechanisms, leading to potential security risks for developers and users alike.
Vulnerability Detail
The vulnerability stems from the package being associated with the tea.xyz token reward campaign, which has been flooding the npm registry with malicious packages. These packages contain scripts that automatically modify the package.json file to remove private flags, alter version numbers, and generate random package names. This behavior not only inflates developer reputation scores but also pollutes the npm registry, making it difficult for users to find legitimate packages. The malicious payload can lead to unauthorized access and manipulation of projects that depend on this package.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall mobile_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 mobile_basilisk_z3n package altogether and look for alternative packages that provide similar functionality without the associated risks. Additionally, consider using tools like Vulert to monitor your package dependencies for vulnerabilities.
Conclusion
The mobile_basilisk_z3n package poses a significant security risk due to its association with malicious activities in the npm ecosystem. It is essential for developers to be vigilant and take proactive measures to protect their projects from such vulnerabilities. Regularly monitoring dependencies and staying informed about potential threats can help maintain the integrity of your applications.
See every vulnerability recorded for mobile_basilisk_z3n →
FAQ
mobile_basilisk_z3n is an npm package that has been identified as part of a malicious campaign targeting the npm registry.
The vulnerability can lead to unauthorized modifications in your project's dependencies, potentially compromising its security and integrity.
You should uninstall the mobile_basilisk_z3n package immediately and look for alternatives. Use 'npm uninstall mobile_basilisk_z3n' to remove it.
Yes, you can use Vulert to monitor your project for open-source vulnerabilities in real-time without needing to access the code.
You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.
