Malicious Code Injection in prospective_guan_z3n Package - npm Vulnerability

prospective_guan_z3n Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-107367: Malicious code in prospective_guan_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 prospective_guan_z3n package is part of the npm ecosystem, often used in JavaScript projects. It is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with various packages. This package, like others in the campaign, is designed to manipulate the npm registry by generating and publishing numerous derivative packages, thereby inflating developer reputation scores for token rewards.

Vulnerability Detail

The vulnerability stems from malicious code embedded within the prospective_guan_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 primary risk is that it can lead to the pollution of the npm registry with numerous unwanted packages, potentially compromising the integrity of the ecosystem and affecting developers who rely on npm for package management.

How To Fix

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

npm uninstall prospective_guan_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 workaround, you can temporarily avoid using the prospective_guan_z3n package in your project until a secure version is released. Additionally, consider using alternative packages that provide similar functionality without the associated risks.

Conclusion

The prospective_guan_z3n package poses a significant risk due to its malicious code that can manipulate the npm registry. It is crucial for developers to remove this package from their projects and monitor for any updates or patches. Utilizing tools like Vulert can help in identifying vulnerabilities in your software effectively.

See every vulnerability recorded for prospective_guan_z3n →

Share this vulnerability

FAQ

It is an npm package associated with the tea.xyz token reward campaign, which has been identified to contain malicious code.

The vulnerability can lead to the pollution of the npm registry, potentially affecting the integrity of your project and introducing unwanted packages.

You should remove the prospective_guan_z3n package from your project immediately to mitigate any risks.

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 use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.

How To Fix

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

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