Malicious Code Injection in super_parrotfish_z3n Package

super_parrotfish_z3n Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-96868: Malicious code in super_parrotfish_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 super_parrotfish_z3n package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. It is designed to facilitate the generation and publication of derivative packages, often with randomized names, to inflate developer reputation scores for token rewards. This package's functionality is compromised due to its malicious intent, which can lead to significant issues in the npm registry.

Vulnerability Detail

The vulnerability in the super_parrotfish_z3n package stems from its inclusion in a malicious campaign that modifies the package.json file to remove private flags and alters version numbers. It generates random package names and continuously republishes variants, which pollutes the npm registry. This behavior can lead to a loss of trust in the npm ecosystem, potential security risks for developers using these packages, and a degradation of the overall quality of available packages.

How To Fix

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

npm uninstall super_parrotfish_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 avoid using the super_parrotfish_z3n package altogether. If it is already in use, consider removing it from your package.json and running npm install to clean up your dependencies.

Conclusion

The super_parrotfish_z3n package is compromised by malicious code that modifies essential files and repackages itself to inflate developer reputation scores. It is crucial to remove this package from your projects and monitor for any updates to maintain the integrity of your applications.

See every vulnerability recorded for super_parrotfish_z3n →

Share this vulnerability

FAQ

The super_parrotfish_z3n package is an npm package associated with a token reward campaign that generates and publishes derivative packages.

This vulnerability can lead to the pollution of the npm registry, affecting the integrity and trustworthiness of packages in your project.

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

Yes, you can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities using just your package-lock.json file.

You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.

How To Fix

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

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