Malicious Code Injection in clumsy_silverfish_z3n: A Threat to npm Packages
Summary
MAL-2025-100623: Malicious code in clumsy_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 'clumsy_silverfish_z3n' is part of a larger ecosystem within npm that has been exploited for malicious purposes. It is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with numerous derivative packages. These packages are designed to inflate developer reputation scores through automated publishing scripts, making them a potential risk for developers and users relying on npm packages.
Vulnerability Detail
The vulnerability in 'clumsy_silverfish_z3n' stems from its malicious payload that modifies the package.json file. This includes removing private flags, altering version numbers, and generating random package names, often themed around Indonesian culture. The malicious scripts continuously republish these variants, leading to pollution of the npm registry and potentially compromising the integrity of other packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall clumsy_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 avoid using the 'clumsy_silverfish_z3n' package and monitor your project for any dependencies that may indirectly rely on it. Consider using tools like Vulert to scan your package-lock.json file for vulnerabilities.
Conclusion
The 'clumsy_silverfish_z3n' package poses a significant risk due to its malicious code that alters package configurations and floods the npm registry. It is essential for developers to take immediate action by removing this package and utilizing tools like Vulert for ongoing vulnerability monitoring.
See every vulnerability recorded for clumsy_silverfish_z3n →
FAQ
The main risk is the modification of your package.json file, which can lead to unauthorized changes in your project and potential exposure to further vulnerabilities.
You can use Vulert to monitor your package-lock.json file for vulnerabilities. It provides real-time alerts for open-source vulnerabilities without requiring code access.
There is no patch for the 'clumsy_silverfish_z3n' package itself; the recommended action is to uninstall it and remove any dependencies that may rely on it.
You should uninstall the package immediately and review your project for any potential security issues that may have arisen from its use.
Yes, regularly audit your dependencies, use tools like Vulert for monitoring, and stay informed about known vulnerabilities in the packages you use.
