Malicious Code Vulnerability in prepared_quail_z3n Package

prepared_quail_z3n Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-107221: Malicious code in prepared_quail_z3n (npm). Affected versions are not published. No fix is published. How to fix ↓

Free scan

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.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The prepared_quail_z3n package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate token rewards through the automatic generation and publication of derivative packages. However, it has been identified as containing malicious code that compromises its integrity and the security of the npm registry.

Vulnerability Detail

The vulnerability in the prepared_quail_z3n package originates from its involvement in a scheme 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 reputation inflation for developers. This behavior not only pollutes the npm registry but also poses a risk to users who may unknowingly install compromised packages.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall prepared_quail_z3n

If 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 prepared_quail_z3n package from your project by executing the following command: npm uninstall prepared_quail_z3n. This will prevent any potential exploitation of the vulnerability until a fix is applied.

Conclusion

The prepared_quail_z3n package is compromised by malicious code that poses significant risks to users and the npm registry. It is crucial to take immediate action by updating or removing the package to safeguard your projects from potential exploitation.

See every vulnerability recorded for prepared_quail_z3n →

Share this vulnerability

FAQ

The prepared_quail_z3n package is an npm package involved in the tea.xyz token reward campaign, which has been found to contain malicious code.

The malicious code modifies your package.json file, removes private flags, and generates random package names, which can lead to security vulnerabilities and reputation inflation.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. You can check your application using the Vulert playground without any signup.

If you cannot update the package right away, consider uninstalling it as a temporary measure to mitigate the risk of exploitation.

More information can be found in the vulnerability report on the official npm registry or by consulting security advisories related to the prepared_quail_z3n package.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall prepared_quail_z3n

If 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 →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback