Malicious Code Injection in voluminous_silverfish_z3n Package

voluminous_silverfish_z3n Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-91985: Malicious code in voluminous_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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The voluminous_silverfish_z3n package is part of a series of npm packages that emerged during the tea.xyz token reward campaign. These packages are designed to inflate developer reputation scores by automatically generating and publishing derivative packages with randomized names. This behavior poses a significant risk as it can lead to the proliferation of malicious code within the npm ecosystem.

Vulnerability Detail

The vulnerability in the voluminous_silverfish_z3n package stems from its malicious payload, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior not only compromises the integrity of the npm registry but also allows for the automatic republishing of these malicious variants, leading to potential exploitation of developers and users who may inadvertently install these packages.

How To Fix

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

npm uninstall voluminous_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 workaround, avoid using the voluminous_silverfish_z3n package and monitor your dependencies for any signs of malicious activity. You can also use tools like Vulert to check for vulnerabilities in your package-lock.json file.

Conclusion

The voluminous_silverfish_z3n package poses a significant security risk due to its malicious behavior of modifying package files and republishing variants. It is crucial to remove this package from your project and monitor your dependencies for any vulnerabilities to maintain the integrity of your software.

See every vulnerability recorded for voluminous_silverfish_z3n →

Share this vulnerability

FAQ

It is an npm package that is part of a malicious campaign to inflate developer reputation scores by flooding the npm registry with derivative packages.

The vulnerability can lead to the installation of malicious code, compromising your project's security and potentially affecting users.

You should immediately uninstall the package using the command npm uninstall voluminous_silverfish_z3n to mitigate any risks.

Yes, you can use Vulert, which monitors your package-lock.json file for open-source vulnerabilities in real-time without requiring code access or installation.

Yes, you can use the Vulert playground at Vulert Scanner to check for vulnerabilities in your application without any signup.

How To Fix

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

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