Malicious Code Injection in Silly Herring Z3N: npm Package Vulnerability
Summary
MAL-2025-90498: Malicious code in silly_herring_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
Silly Herring Z3N is an npm package that has been identified as part of a broader campaign to exploit the npm registry. It is designed to facilitate the automatic generation and publication of derivative packages, often with randomized names. This behavior is linked to attempts to inflate developer reputation scores for token rewards associated with the tea.xyz protocol. The package's functionality is compromised by malicious scripts that manipulate its metadata.
Vulnerability Detail
The vulnerability originates from the package's inclusion in a malicious campaign that floods the npm registry with derivative packages. The malicious code modifies the package.json file by removing private flags, altering version numbers, and generating random package names. This leads to the continuous republishing of variants, polluting the npm registry and potentially affecting other developers and applications relying on legitimate packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall silly_herring_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 using npm's package-lock.json file to monitor dependencies. Ensure that you do not include this package in your project's dependencies and regularly audit your packages for vulnerabilities.
Conclusion
The silly_herring_z3n npm package has been identified as containing malicious code that can compromise the integrity of the npm registry. It is essential to remove this package from your projects and utilize tools like Vulert for ongoing monitoring of vulnerabilities in your dependencies.
See every vulnerability recorded for silly_herring_z3n →
FAQ
The malicious code can lead to the pollution of the npm registry, affecting the integrity of other packages and potentially compromising the security of applications that depend on them.
You can use Vulert to monitor your application for vulnerabilities. By analyzing your package-lock.json file, Vulert provides real-time alerts for any open-source vulnerabilities.
Regularly auditing your dependencies and using tools like Vulert can help identify and mitigate vulnerabilities before they impact your application.
You should uninstall the package immediately using the command npm uninstall silly_herring_z3n and check for any dependencies that may be affected.
Yes, you can use npm packages safely by regularly auditing your dependencies and utilizing tools like Vulert to monitor for vulnerabilities.
