Malicious Code Injection in past_frog_z3n Package: npm Vulnerability Overview

past_frog_z3n Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-89363: Malicious code in past_frog_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 past_frog_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 automatic generation and publication of derivative packages, often with randomized names. It aims to inflate developer reputation scores for token rewards, but it has been identified as containing malicious code that compromises the integrity of the npm registry.

Vulnerability Detail

The vulnerability in the past_frog_z3n package originates from its malicious payload, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior leads to the continuous republishing of variants, effectively polluting the npm registry. The ramifications include potential security risks for developers who unknowingly use these compromised packages, as well as a degradation of trust in the npm ecosystem.

How To Fix

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

npm uninstall past_frog_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 past_frog_z3n package from your project by executing the command: 'npm uninstall past_frog_z3n'. This will prevent any malicious code from executing in your environment until a patch is available.

Conclusion

The past_frog_z3n package has been identified as containing malicious code that poses a significant risk to developers using it. It is crucial to update or remove this package to maintain the security of your projects. Utilizing tools like Vulert can help you stay informed about vulnerabilities in your dependencies.

See every vulnerability recorded for past_frog_z3n →

Share this vulnerability

FAQ

The past_frog_z3n package is an npm package associated with the tea.xyz token reward campaign, designed to automatically generate and publish derivative packages.

The vulnerability can lead to the modification of your package.json file and the introduction of malicious code, which can compromise your project's security.

Yes, you can use Vulert to monitor and alert for open-source vulnerabilities in your software. You can check your application for this specific vulnerability using the Vulert playground without any signup.

If you cannot update the package, consider uninstalling it as a temporary measure to avoid potential security risks.

You can find detailed information about this vulnerability in the official npm registry or through security advisories related to the past_frog_z3n package.

How To Fix

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

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