Malicious Code Injection in moderate_silverfish_z3n: A Threat to npm Packages
Summary
MAL-2025-95522: Malicious code in moderate_silverfish_z3n (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 package 'moderate_silverfish_z3n' is part of the npm ecosystem, which is widely used for JavaScript package management. This package has been identified as part of a malicious campaign that aims to exploit the npm registry by flooding it with derivative packages. These packages are designed to inflate developer reputation scores through automated publishing scripts, making them a significant threat to the integrity of the npm ecosystem.
Vulnerability Detail
The vulnerability in 'moderate_silverfish_z3n' originates from its association with the tea.xyz token reward campaign. It contains scripts that modify the package.json file to remove private flags, alter version numbers, and generate random package names. This behavior leads to the continuous republishing of variants, which pollutes the npm registry and can potentially compromise other packages and projects relying on npm.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall moderate_silverfish_z3nIf 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 prevent the installation of this package by adding it to your project's .npmrc file with the following line: 'npm_config_ignore_scripts=true'. This will disable the execution of scripts during installation, but it is recommended to remove the package entirely.
Conclusion
The 'moderate_silverfish_z3n' package poses a significant threat due to its malicious code designed to manipulate the npm registry. It is essential to take immediate action by removing the package and using tools like Vulert to monitor for vulnerabilities in your projects. Staying informed and cautious can help maintain the integrity of your software dependencies.
See every vulnerability recorded for moderate_silverfish_z3n →
FAQ
The malicious code can lead to the pollution of the npm registry, affecting the reputation of developers and potentially compromising other packages.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. By analyzing your package-lock.json file, Vulert can help you identify affected packages.
Regularly audit your dependencies and use tools like Vulert to monitor for vulnerabilities. Always be cautious when adding new packages from unverified sources.
Immediately remove the package from your project and check for any updates or patches that may address the vulnerability.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.
