Malicious Code Injection in valid_dolphin_z3n Package

valid_dolphin_z3n Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-97219: Malicious code in valid_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 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 valid_dolphin_z3n package is part of the npm ecosystem, which is widely used for JavaScript development. This package, like many others, is intended to facilitate various functionalities within applications. However, it has been identified as part of a malicious campaign that aims to exploit the npm registry by flooding it with derivative packages that can inflate developer reputation scores for token rewards.

Vulnerability Detail

The vulnerability in the valid_dolphin_z3n package stems from its association with a malicious campaign that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior is designed to continuously republish variants of the package, polluting the npm registry and potentially compromising the integrity of applications that rely on it. The malicious payload can lead to unauthorized access, data leakage, and a compromised development environment.

How To Fix

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

npm uninstall valid_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 workaround, you can avoid using the valid_dolphin_z3n package and replace it with a trusted alternative that offers similar functionality. Additionally, ensure that your package-lock.json is monitored for any unauthorized changes.

Conclusion

The valid_dolphin_z3n package poses a significant risk due to its malicious code that alters package metadata and floods the npm registry. It is crucial to remove this package from your projects and monitor for vulnerabilities to maintain the integrity of your applications.

See every vulnerability recorded for valid_dolphin_z3n →

Share this vulnerability

FAQ

valid_dolphin_z3n is an npm package that has been identified as part of a malicious campaign to manipulate the npm registry.

The vulnerability can lead to unauthorized modifications in your application's dependencies, potentially compromising security and functionality.

You should uninstall the valid_dolphin_z3n package immediately and monitor your application for any unusual behavior.

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

You can use the Vulert playground at Vulert Scanner to check if your application is affected without needing to sign up.

How To Fix

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

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