Malicious Code Injection in original_quail_z3n Package: A Threat to npm Users
Summary
MAL-2025-89324: Malicious code in original_quail_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 original_quail_z3n package is part of the npm ecosystem, which is widely used for managing JavaScript packages. 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 aims to exploit npm's publishing system, thereby compromising the integrity of the registry and the applications that depend on it.
Vulnerability Detail
The vulnerability in the original_quail_z3n package arises from its inclusion in a malicious campaign associated with the tea.xyz token reward initiative. This package contains scripts designed to automatically generate and publish derivative packages with randomized names, effectively polluting the npm registry. The malicious payload modifies the package.json file to remove private flags, alters version numbers, and continuously republishes variants, which can lead to a loss of trust in the npm ecosystem and potential security risks for developers using these packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall original_quail_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 original_quail_z3n package and replace it with a similar, trusted package that does not exhibit malicious behavior. Always review the packages you include in your project for any known vulnerabilities.
Conclusion
The original_quail_z3n package poses a significant threat to npm users due to its malicious behavior aimed at exploiting the npm registry. It is crucial for developers to remain vigilant, regularly check for vulnerabilities, and utilize tools like Vulert to ensure their applications are secure. By taking proactive measures, such as uninstalling compromised packages and replacing them with trusted alternatives, developers can protect their projects from potential risks.
See every vulnerability recorded for original_quail_z3n →
FAQ
The original_quail_z3n package is an npm package that has been identified as part of a malicious campaign aimed at exploiting the npm registry.
You can use tools like Vulert to monitor and alert you for open-source vulnerabilities in your software. By analyzing your package-lock.json file, Vulert can help identify if your application is affected.
If you have installed the original_quail_z3n package, you should uninstall it immediately using 'npm uninstall original_quail_z3n' and replace it with a trusted alternative.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.
Using compromised packages can lead to security vulnerabilities, data breaches, and a loss of trust in the software supply chain, potentially affecting your application's integrity and user data.
