Malicious Code Exploit in separate_snail_z3n Package: npm Vulnerability Overview
Summary
MAL-2025-108555: Malicious code in separate_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 separate_snail_z3n package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate the automatic generation and publication of derivative packages, which can inflate developer reputation scores for token rewards. However, it has been identified as containing malicious code that compromises its integrity and the npm registry.
Vulnerability Detail
The vulnerability in the separate_snail_z3n package stems from its malicious payload, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior is intended to continuously republish variants, leading to pollution of the npm registry and potential exploitation of developers' reputations. The origin of this issue is linked to the broader trend of malicious packages flooding the npm ecosystem, particularly those associated with token reward schemes.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall separate_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 separate_snail_z3n package from your project by executing: npm uninstall separate_snail_z3n. This will prevent any malicious code from executing while you seek a secure alternative or patch.
Conclusion
The separate_snail_z3n package has been identified as containing malicious code that poses a significant risk to developers and the npm ecosystem. It is crucial to take immediate action by updating or removing the package to safeguard your projects. Utilizing tools like Vulert can help monitor and alert you to such vulnerabilities in real-time.
See every vulnerability recorded for separate_snail_z3n →
FAQ
The separate_snail_z3n package is an npm package involved in the tea.xyz token reward campaign, designed to automate the generation and publication of derivative packages.
The vulnerability can lead to the pollution of the npm registry and may compromise your project's integrity by allowing malicious code to execute.
If you have installed the separate_snail_z3n package, it is recommended to uninstall it immediately and check for any updates or patches.
Yes, you can use Vulert to monitor your project for open-source vulnerabilities in real-time. Vulert uses package-lock.json to alert you of any issues without requiring code access.
You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.
