Malicious Code Injection in quintessential_perch_z3n: A Threat to npm Ecosystem

quintessential_perch_z3n Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-96166: Malicious code in quintessential_perch_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

quintessential_perch_z3n is an npm package that has been identified as part of a malicious campaign targeting the npm registry. This package is associated with the tea.xyz token reward initiative, which has been known to flood the npm ecosystem with harmful packages. The primary function of this package appears to be the automatic generation and publication of derivative packages, which can compromise the integrity of the npm registry and inflate developer reputation scores.

Vulnerability Detail

The vulnerability stems from the malicious code embedded within the quintessential_perch_z3n package. This code is designed to modify the package.json file by removing private flags, altering version numbers, and generating random package names. The malicious payload continuously republishes these variants, leading to pollution of the npm registry. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which exploits npm's publishing mechanisms to distribute harmful packages.

How To Fix

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

npm uninstall quintessential_perch_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 prevent the installation of the quintessential_perch_z3n package by using npm's package-lock.json file to lock your dependencies. This will help avoid unintentional updates that may include the malicious package. You can also monitor your dependencies using tools like Vulert, which alerts you to open-source vulnerabilities in real-time.

Conclusion

The quintessential_perch_z3n package poses a significant threat to the npm ecosystem due to its malicious code designed to manipulate package metadata and republish harmful variants. It is crucial for developers to take immediate action to remove this package and monitor their projects for vulnerabilities to maintain security.

See every vulnerability recorded for quintessential_perch_z3n →

Share this vulnerability

FAQ

quintessential_perch_z3n is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores through the automatic generation of harmful packages.

The vulnerability can lead to the pollution of the npm registry, potentially compromising your project's integrity and security by introducing malicious code.

You should uninstall the quintessential_perch_z3n package immediately using the command npm uninstall quintessential_perch_z3n and check your project for any other affected dependencies.

You can use Vulert to monitor your project for open-source vulnerabilities in real-time. It requires only your package-lock.json file and does not need any code access or installation.

Regularly update your dependencies, use tools like Vulert for monitoring, and audit your packages to ensure they are from trusted sources.

How To Fix

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

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