Malicious Code Vulnerability in experimental_perch_z3n Package

experimental_perch_z3n Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-94386: Malicious code in experimental_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 Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The experimental_perch_z3n package is part of the npm ecosystem, which is used for managing JavaScript packages. This package has been identified as part of a larger malicious campaign that aims to manipulate the npm registry by flooding it with derivative packages. The primary functionality of this package is to serve as a token reward mechanism for the tea.xyz project, but it has been compromised to include harmful scripts.

Vulnerability Detail

The vulnerability originates from the package being associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with malicious packages. These packages contain scripts that automatically modify the package.json file to remove private flags, alter version numbers, and generate random package names. This behavior can lead to the pollution of the npm registry, potentially harming developers' reputations and causing security risks in applications that depend on these packages.

How To Fix

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

npm uninstall experimental_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 avoid using the experimental_perch_z3n package and monitor your package dependencies for any signs of malicious activity. Additionally, consider using tools like Vulert to monitor your project for vulnerabilities. You can check if your application is affected by this vulnerability using the Vulert playground at https://vulert.com/scanner without any signup.

Conclusion

The experimental_perch_z3n package has been identified as a malicious entity within the npm ecosystem, posing significant risks to developers and their applications. It is crucial to remove this package and monitor for any updates or patches to ensure the security of your projects.

See every vulnerability recorded for experimental_perch_z3n →

Share this vulnerability

FAQ

It is an npm package that is part of a token reward campaign but has been compromised to include malicious code.

The vulnerability can lead to the pollution of the npm registry and may compromise the integrity of your application by introducing malicious code.

You should remove the experimental_perch_z3n package from your project immediately and monitor for any updates or patches.

You can use tools like Vulert, which monitors your package-lock.json for vulnerabilities in real-time.

Yes, you can use the Vulert playground at Vulert Scanner to check for vulnerabilities without needing to sign up.

How To Fix

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

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