Malicious Code Injection in mighty_sailfish_z3n: npm Package Vulnerability

mighty_sailfish_z3n Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-95470: Malicious code in mighty_sailfish_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 mighty_sailfish_z3n package is part of the npm ecosystem, which is widely used for JavaScript package management. This package is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with malicious packages. The primary functionality of this package is to serve as a token reward mechanism, but it has been compromised to include harmful scripts that manipulate package metadata.

Vulnerability Detail

The vulnerability in mighty_sailfish_z3n stems from its inclusion in a malicious campaign that generates and publishes derivative packages with randomized names. This is achieved through scripts that modify the package.json file, removing private flags, altering version numbers, and creating numerous variants to inflate developer reputation scores. The malicious payload can lead to pollution of the npm registry, making it difficult for developers to find legitimate packages and potentially exposing users to further security risks.

How To Fix

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

npm uninstall mighty_sailfish_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 mighty_sailfish_z3n package and look for alternative packages that provide similar functionality without the associated risks. Additionally, you can use the following command to uninstall the package: npm uninstall mighty_sailfish_z3n.

Conclusion

The mighty_sailfish_z3n package has been identified as a vector for malicious code that compromises the integrity of the npm registry. It is crucial for developers to remove this package and monitor their dependencies for similar vulnerabilities to maintain the security of their applications.

See every vulnerability recorded for mighty_sailfish_z3n →

Share this vulnerability

FAQ

The vulnerability involves malicious code that modifies package metadata and floods the npm registry with derivative packages.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. By checking your package-lock.json file, you can determine if your application is affected.

You should uninstall the mighty_sailfish_z3n package immediately and look for alternative packages. If a patched version is available, update to that version.

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

Failing to address this vulnerability can lead to exposure to further security risks, including the use of compromised packages that may harm your application or its users.

How To Fix

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

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