Malicious Code Injection in verbal_silverfish_requirement Package
Summary
MAL-2025-97246: Malicious code in verbal_silverfish_requirement (npm). Affected versions are not published. No fix is published. How to fix ↓
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.
No signup required · Results in about 60 seconds
Background
The verbal_silverfish_requirement package is part of the npm ecosystem, often used in JavaScript projects. It is designed to facilitate various functionalities within applications. However, this package has been identified as part of a malicious campaign that floods the npm registry with derivative packages, potentially compromising the integrity of projects that depend on it.
Vulnerability Detail
The vulnerability originates from the package being associated with a token reward campaign that utilizes autopublish scripts to generate and publish numerous derivative packages with randomized names. This behavior not only inflates developer reputation scores but also modifies the package.json file to remove private flags, alters version numbers, and continuously republishes variants, leading to pollution of the npm registry. The ramifications include potential security risks for developers who unknowingly integrate these compromised packages into their projects.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall verbal_silverfish_requirementIf 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, consider removing the verbal_silverfish_requirement package from your project until a secure version is confirmed. You can do this by executing the command: npm uninstall verbal_silverfish_requirement.
Conclusion
The verbal_silverfish_requirement package poses a significant security risk due to its association with malicious code designed to manipulate npm registry entries. It is essential for developers to take proactive measures, including updating or removing the package, to safeguard their projects from potential threats.
See every vulnerability recorded for verbal_silverfish_requirement →
FAQ
The vulnerability involves malicious code that modifies package.json files and floods the npm registry with derivative packages.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without requiring any signup.
Using this package can lead to security risks, including the potential exposure of sensitive information and the introduction of unstable or malicious code into your project.
Regularly audit your dependencies and utilize tools like Vulert to monitor for vulnerabilities in your open-source packages.
If an immediate update is not possible, consider removing the package from your project as a temporary measure until a secure version is available.
