Malicious Code Exploit in Functional Dolphin Z3N Package

functional_dolphin_z3n Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-94632: Malicious code in functional_dolphin_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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

Functional Dolphin Z3N is an npm package that is part of the tea.xyz token reward campaign. It is designed to facilitate token rewards for developers by generating and publishing derivative packages. However, this package has been compromised, leading to significant security concerns due to its malicious functionalities.

Vulnerability Detail

The vulnerability originates from the package being part of a malicious campaign that floods the npm registry with fake packages. It contains scripts that modify the package.json file to remove private flags, change version numbers, and generate random package names. This results in the continuous republishing of variants, which can pollute the npm registry and inflate developer reputation scores fraudulently. The malicious payload can lead to unauthorized access and manipulation of the package ecosystem, posing a risk to developers and users relying on these packages.

How To Fix

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

npm uninstall functional_dolphin_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 measure, avoid using the functional_dolphin_z3n package until a secure version is released. Regularly monitor your dependencies and consider using tools like Vulert to track vulnerabilities in your project.

Conclusion

The functional_dolphin_z3n package has been identified as containing malicious code that can compromise the integrity of your project. It is crucial to uninstall this package and monitor your dependencies closely. Utilizing tools like Vulert can help you stay ahead of potential vulnerabilities.

See every vulnerability recorded for functional_dolphin_z3n →

Share this vulnerability

FAQ

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

The vulnerability can lead to unauthorized modifications in your package.json file, potentially compromising your project and its dependencies.

You should uninstall the functional_dolphin_z3n package immediately and monitor your project for any unusual activity.

Yes, Vulert allows you to monitor and alert for open-source vulnerabilities in your software using just the package-lock.json file.

Regularly audit your dependencies and use tools like Vulert to stay informed about vulnerabilities in your packages.

How To Fix

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

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