Malicious Code Vulnerability in previous_snail_z3n Package
Summary
MAL-2025-96009: Malicious code in previous_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 previous_snail_z3n package 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 generation of derivative packages. The malicious nature of this package lies in its ability to modify critical files and republish variants, thereby polluting the npm registry.
Vulnerability Detail
The vulnerability originates from the previous_snail_z3n package being associated with the tea.xyz token reward campaign. It contains scripts designed to automatically publish derivative packages with randomized names, which can lead to the removal of private flags in package.json files and changes to version numbers. This behavior not only compromises the integrity of the npm registry but also poses a risk to developers who may unknowingly use these compromised packages, potentially leading to security breaches in their applications.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall previous_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 remove the previous_snail_z3n package from your project by executing the following command: npm uninstall previous_snail_z3n. This will prevent any malicious code from executing in your application.
Conclusion
The previous_snail_z3n package poses a significant risk due to its malicious code that alters package files and repopulates the npm registry with compromised versions. It is crucial for developers to take immediate action by updating or removing the package to safeguard their applications.
See every vulnerability recorded for previous_snail_z3n →
FAQ
The previous_snail_z3n package is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores.
This vulnerability can lead to the modification of critical files in your application, potentially exposing it to security risks and compromising its integrity.
If you have the previous_snail_z3n package installed, you should uninstall it immediately or update it to a patched version if available.
Yes, you can use Vulert to monitor and alert in real-time for open-source vulnerabilities in your software. It requires only the package-lock.json file.
You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.
