Malicious Code Injection in tiny_sailfish_z3n: A Threat to npm Packages

tiny_sailfish_z3n Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-97020: Malicious code in tiny_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 tiny_sailfish_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 on npm. Its functionality is compromised by the presence of malicious scripts that manipulate package metadata, posing a risk to developers and users alike.

Vulnerability Detail

The vulnerability stems from the presence of malicious code within the tiny_sailfish_z3n package. This code is designed to automatically modify the package.json file by removing private flags, altering version numbers, and generating random package names. The malicious payload aims to inflate developer reputation scores through the creation and republishing of derivative packages, which can lead to pollution of the npm registry and potential exploitation of unsuspecting users.

How To Fix

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

npm uninstall tiny_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 remove the tiny_sailfish_z3n package from your project by executing the command: npm uninstall tiny_sailfish_z3n. This will prevent any malicious code from executing until a secure version is available.

Conclusion

The tiny_sailfish_z3n package poses a significant security risk due to its malicious code designed to manipulate package metadata. It is essential for developers to take immediate action by updating or removing the package and to implement monitoring tools like Vulert to safeguard their projects against future vulnerabilities.

See every vulnerability recorded for tiny_sailfish_z3n →

Share this vulnerability

FAQ

tiny_sailfish_z3n is an npm package that has been identified as containing malicious code aimed at manipulating package metadata and inflating developer reputation scores.

The malicious code can alter your package.json file, remove private flags, and create numerous derivative packages, which can lead to security vulnerabilities and pollution of the npm registry.

If you have installed tiny_sailfish_z3n, it is recommended to uninstall the package immediately and check for any updates or patches that may address the vulnerability.

You can use tools like Vulert, which monitors your package-lock.json file to alert you in real-time about open-source vulnerabilities in your software. You can also check your application for vulnerabilities using the Vulert playground without any signup.

To prevent future vulnerabilities, regularly update your dependencies, use trusted sources for packages, and consider employing automated security scanning tools.

How To Fix

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

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