Malicious Code Injection in ready_silverfish_z3n: A Threat to npm Packages
Summary
MAL-2025-89898: Malicious code in ready_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 'ready_silverfish_z3n' is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to automate the generation and publication of derivative packages, which can lead to reputation inflation for developers involved in the tea protocol. However, it has been compromised to include malicious scripts that can manipulate package metadata.
Vulnerability Detail
The vulnerability stems from malicious code embedded within the 'ready_silverfish_z3n' package. This code modifies the package.json file to remove private flags, alters version numbers, and generates random package names, which can lead to the pollution of the npm registry. The origin of this issue is linked to a broader trend of malicious packages flooding the npm ecosystem, aimed at exploiting developer reputation systems for token rewards.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall ready_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 malicious package by using npm's package-lock.json to monitor your dependencies. Ensure that your project does not include 'ready_silverfish_z3n' in its dependencies. Additionally, consider using tools like Vulert to monitor your project for vulnerabilities in real-time.
Conclusion
The 'ready_silverfish_z3n' package poses a significant risk due to its malicious code that alters package metadata and pollutes the npm registry. It is vital for developers to remove this package and utilize tools like Vulert to safeguard their projects against such vulnerabilities.
See every vulnerability recorded for ready_silverfish_z3n →
FAQ
The malicious code can lead to unauthorized changes in your package.json file, potentially exposing your project to further vulnerabilities and affecting the integrity of the npm registry.
You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.
If you have installed this package, you should uninstall it immediately using 'npm uninstall ready_silverfish_z3n' and check for any dependencies that may be affected.
Yes, tools like Vulert can help monitor your project for open-source vulnerabilities in real-time, using just your package-lock.json.
Using compromised packages can lead to security breaches, data loss, and damage to your project's reputation, making it crucial to regularly audit and monitor your dependencies.
