Malicious Code Injection in Significant Parrotfish Z3N Package

significant_parrotfish_z3n Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-96584: Malicious code in significant_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 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 Significant Parrotfish Z3N package is part of the npm ecosystem, which is widely used for JavaScript package management. This package is suspected to be involved in a token reward campaign that has led to the proliferation of malicious packages within the npm registry. The primary function of this package is to facilitate the distribution of JavaScript code, but it has been compromised to serve malicious purposes.

Vulnerability Detail

The vulnerability originates from the package being part of a broader scheme to inflate developer reputation scores through the automatic generation and publication of derivative packages. The malicious code modifies the package.json file to remove private flags, alters version numbers, and generates random package names, leading to pollution of the npm registry. This not only affects the integrity of the npm ecosystem but also poses security risks to developers who may unknowingly use these compromised packages.

How To Fix

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

npm uninstall significant_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 an immediate workaround, you can avoid using the Significant Parrotfish Z3N package and monitor your package-lock.json file for any dependencies that may include it. Additionally, consider using tools like Vulert to monitor your project for vulnerabilities.

Conclusion

The Significant Parrotfish Z3N package has been identified as a malicious entity within the npm ecosystem, posing significant risks to developers and their projects. Immediate action is required to remove this package and monitor for any vulnerabilities using tools like Vulert.

See every vulnerability recorded for significant_parrotfish_z3n →

Share this vulnerability

FAQ

It is an npm package that has been identified as malicious, involved in a scheme to inflate developer reputation scores.

The vulnerability can lead to the introduction of malicious code into your project, potentially compromising its security and integrity.

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

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

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

How To Fix

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

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