Malicious Code Injection in governing_silverfish-strongdev Package

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-103320: Malicious code in governing_silverfish-strongdev (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 governing_silverfish-strongdev package is part of the npm ecosystem, primarily used for various development tasks. However, it has been identified as part of a malicious campaign that floods the npm registry with derivative packages. This package is designed to inflate developer reputation scores through automated scripts that publish numerous variants of itself, often with altered names and configurations.

Vulnerability Detail

The vulnerability originates from the package being part of a token reward campaign that employs malicious scripts to modify the package.json file. These scripts remove private flags, alter version numbers, and generate random package names, leading to pollution of the npm registry. This can result in developers unknowingly using compromised packages, which may expose their applications to further vulnerabilities and security risks.

How To Fix

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

npm uninstall governing_silverfish-strongdev

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 governing_silverfish-strongdev package altogether and look for alternative packages that provide similar functionality without the associated risks.

Conclusion

The governing_silverfish-strongdev package poses a significant security risk due to its malicious code designed to manipulate npm registry data. It is crucial for developers to remove this package and monitor their projects for vulnerabilities to ensure application security.

See every vulnerability recorded for governing_silverfish-strongdev →

Share this vulnerability

FAQ

It is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores.

Using this package can lead to the introduction of malicious code, which may compromise your application's security and integrity.

You should uninstall the governing_silverfish-strongdev package immediately to mitigate any potential risks.

Yes, you can use tools like Vulert, which monitors your package-lock.json for open-source vulnerabilities in real-time.

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 governing_silverfish-strongdev

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