Malicious Code Injection in superb_silverfish_z3n: A Threat to npm Packages

superb_silverfish_z3n Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-96870: Malicious code in superb_silverfish_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 superb_silverfish_z3n package is part of the npm ecosystem, which is widely used for JavaScript package management. This package appears to be associated with a token reward campaign that has led to the proliferation of malicious packages in the npm registry. Its primary function is to facilitate the distribution of software, but it has been compromised to include harmful scripts that manipulate package metadata.

Vulnerability Detail

The vulnerability in superb_silverfish_z3n originates from its design to automatically generate and publish derivative packages with randomized names. This malicious behavior includes modifying the package.json file to remove private flags, altering version numbers, and continuously republishing variants to pollute the npm registry. The implications of this vulnerability are significant, as it can lead to the misuse of developer reputation scores and the potential distribution of harmful software to unsuspecting users.

How To Fix

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

npm uninstall superb_silverfish_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, you can prevent the installation of this malicious package by using npm's package-lock.json to monitor dependencies. Ensure that your project does not include superb_silverfish_z3n in its dependencies.

Conclusion

The superb_silverfish_z3n package poses a significant threat due to its malicious code that alters package metadata and inflates developer reputation scores. It is crucial for developers to remove this package from their projects and utilize tools like Vulert to monitor for vulnerabilities in real-time.

See every vulnerability recorded for superb_silverfish_z3n →

Share this vulnerability

FAQ

superb_silverfish_z3n is an npm package that has been identified as malicious, designed to manipulate package metadata and inflate developer reputation scores.

This vulnerability can lead to the installation of harmful software, manipulation of your project's dependencies, and potential damage to your developer reputation.

You should immediately uninstall the superb_silverfish_z3n package using the command: npm uninstall superb_silverfish_z3n.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time using just your package-lock.json file. You can check your application for vulnerabilities using the Vulert playground at Vulert Scanner.

Regularly audit your dependencies, use tools like Vulert for monitoring, and stay updated on security advisories related to the packages you use.

How To Fix

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

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