Malicious Code Injection in static_snail_z3n: A Threat to npm Ecosystem
Summary
MAL-2025-109085: Malicious code in static_snail_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 'static_snail_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 inflate developer reputation scores through the creation and publication of derivative packages. The malicious nature of this package compromises the integrity of the npm registry and poses a risk to developers and users relying on legitimate packages.
Vulnerability Detail
The vulnerability in 'static_snail_z3n' originates from its association with the tea.xyz token reward campaign. It contains scripts designed to automatically generate and publish derivative packages with randomized names, effectively polluting the npm registry. The malicious payload modifies the package.json file to remove private flags, alters version numbers, and continuously republishes variants, which can lead to confusion and potential security risks for users who may inadvertently install these compromised packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall static_snail_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 'static_snail_z3n' package altogether. If it is already included in your project, remove it by executing the following command: npm uninstall static_snail_z3n. Additionally, consider using Vulert to monitor your project for vulnerabilities. You can check if your application is affected by this vulnerability using the Vulert playground at https://vulert.com/scanner without any signup.
Conclusion
The 'static_snail_z3n' package poses a significant threat due to its malicious code designed to manipulate the npm registry. Developers should take immediate action to remove this package and monitor their projects for vulnerabilities using tools like Vulert. Staying informed and proactive is crucial in maintaining the security of your applications.
See every vulnerability recorded for static_snail_z3n →
FAQ
The primary risk is that it can lead to the installation of malicious code, which may compromise the security of your application and the integrity of the npm registry.
You can use the Vulert playground at Vulert Scanner to check if your application is affected without needing to sign up.
You should uninstall the package immediately using the command: npm uninstall static_snail_z3n.
Currently, there are no patches available for this package. It is recommended to remove it from your project.
Vulert uses your package-lock.json file to monitor and alert you in real-time for open-source vulnerabilities in your software, ensuring you stay informed about potential risks.
