Malicious Code Injection in early_sailfish_z3n Package - npm Vulnerability

early_sailfish_z3n Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-132957: Malicious code in early_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 early_sailfish_z3n package is part of the npm ecosystem, which is widely used for JavaScript package management. This package has been identified as part of a malicious campaign that aims to exploit the npm registry by flooding it with derivative packages. These packages are designed to inflate developer reputation scores for token rewards, making them a significant threat to the integrity of the npm ecosystem.

Vulnerability Detail

The vulnerability in the early_sailfish_z3n package stems from its malicious code, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior leads to the continuous republishing of variants, polluting the npm registry and potentially compromising the security of applications that depend on these packages. The origin of this vulnerability is linked to a campaign that leverages autopublish scripts to automate the creation and distribution of these malicious packages.

How To Fix

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

npm uninstall early_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 early_sailfish_z3n package and any other packages that are part of the malicious campaign. Additionally, you can use npm audit to identify and address vulnerabilities in your dependencies.

Conclusion

The early_sailfish_z3n package has been identified as a malicious package that poses a significant threat to the npm ecosystem. It is crucial for developers to be aware of this vulnerability and take appropriate actions to secure their applications.

See every vulnerability recorded for early_sailfish_z3n →

Share this vulnerability

FAQ

The early_sailfish_z3n package is an npm package that has been identified as part of a malicious campaign to exploit the npm registry.

This vulnerability can lead to the pollution of the npm registry and may compromise the security of applications that depend on the affected package.

You should update the package to a patched version if available or remove it from your project to mitigate the risk.

You can use tools like Vulert, which monitors and alerts in real-time for open-source vulnerabilities using just package-lock.json.

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

How To Fix

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

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