Malicious Code Injection in general_quail_z3n Package - npm Vulnerability

general_quail_z3n Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-94662: Malicious code in general_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 Devnack Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The general_quail_z3n package is part of the npm ecosystem, which is widely used for JavaScript package management. This package is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with malicious packages. The primary functionality of such packages is to generate and publish derivative packages to inflate developer reputation scores for token rewards. However, this specific package has been compromised, making it a potential threat to users.

Vulnerability Detail

The vulnerability in the general_quail_z3n package stems from its malicious code that modifies the package.json file. It removes private flags, alters version numbers, and generates random package names, which can lead to the pollution of the npm registry. This behavior not only compromises the integrity of the package but also poses risks to developers who may unknowingly install these malicious variants. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which employs autopublish scripts to automate the generation of these harmful packages.

How To Fix

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

npm uninstall general_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 general_quail_z3n package from your project by executing the following command: npm uninstall general_quail_z3n. This will prevent any malicious code from executing while you seek a secure alternative.

Conclusion

The general_quail_z3n package has been identified as containing malicious code that poses a significant risk to developers and their projects. It is essential to take immediate action by updating or removing the package to safeguard your application. Utilizing tools like Vulert can help monitor and alert you to such vulnerabilities in real-time.

See every vulnerability recorded for general_quail_z3n →

Share this vulnerability

FAQ

The general_quail_z3n package is a JavaScript package in the npm ecosystem, primarily associated with the tea.xyz token reward campaign.

The malicious code modifies your package.json file, potentially leading to the installation of harmful packages and compromising your project's integrity.

If you have installed the general_quail_z3n package, it is crucial to uninstall it immediately and check for any other affected packages.

Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in your software using just the package-lock.json file. You can also check your application for vulnerabilities using the Vulert playground.

You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.

How To Fix

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

npm uninstall general_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