Malicious Code Injection in Rising Quail Z3N Package

rising_quail_z3n Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-90225: Malicious code in rising_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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The 'rising_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 the generation and publication of derivative packages, often with randomized names, to inflate developer reputation scores for token rewards. However, it has been identified as containing malicious code that compromises its integrity.

Vulnerability Detail

The vulnerability originates from the package's malicious payload, which modifies the package.json file by removing private flags, altering version numbers, and generating random package names. This behavior leads to the continuous republishing of variants, polluting the npm registry and potentially affecting other developers and applications relying on the npm ecosystem. The malicious scripts (auto.js, autopublish.js, etc.) are designed to automate this process, making it difficult to track and mitigate.

How To Fix

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

npm uninstall rising_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 measure, you can prevent the installation of the 'rising_quail_z3n' package by adding it to your project's .npmrc file with the following line: 'package-lock=false'. This will help avoid the automatic installation of this malicious package until a fix is implemented.

Conclusion

The 'rising_quail_z3n' package poses a significant security risk due to its malicious code that alters package configurations and repopulates the npm registry with harmful variants. It is crucial to remove this package from your projects and monitor your dependencies for vulnerabilities to maintain application security.

See every vulnerability recorded for rising_quail_z3n →

Share this vulnerability

FAQ

The 'rising_quail_z3n' package is an npm package involved in the tea.xyz token reward campaign, designed to inflate developer reputation scores through automated package publishing.

The vulnerability can lead to the injection of malicious code into your application, potentially compromising its security and integrity by modifying package configurations and republishing harmful variants.

If you have installed the 'rising_quail_z3n' package, you should uninstall it immediately using 'npm uninstall rising_quail_z3n' and check for any dependencies that may be affected.

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 check your application for vulnerabilities without any signup at the Vulert playground.

Regularly audit your dependencies using tools like npm audit, keep your packages updated, and consider using vulnerability monitoring services like Vulert to receive real-time alerts.

How To Fix

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

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