Malicious Code Injection in unknown_snail_z3n Package - npm Vulnerability

unknown_snail_z3n Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-110155: Malicious code in unknown_snail_z3n (npm). Affected versions are not published. No fix is published. How to fix ↓

Free scan

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.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The unknown_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.

Vulnerability Detail

The vulnerability originates from the package's design to include autopublish scripts that modify the package.json file by removing private flags and changing version numbers. It generates random package names, often themed around Indonesian culture, and continuously republishes these variants, leading to pollution of the npm registry. This behavior can result in security risks, including the potential for unauthorized access to sensitive information and the degradation of the npm ecosystem's reliability.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall unknown_snail_z3n

If 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 unknown_snail_z3n package and monitor your project for any dependencies that may inadvertently include it. Regularly audit your package-lock.json file to identify any potentially malicious packages.

Conclusion

The unknown_snail_z3n package poses a significant security risk due to its malicious code that alters package configurations and repopulates the npm registry with potentially harmful variants. It is crucial to remove this package from your projects and monitor for any dependencies that may include it.

See every vulnerability recorded for unknown_snail_z3n →

Share this vulnerability

FAQ

The unknown_snail_z3n package is an npm package associated with a token reward campaign that has been identified to contain malicious code.

The malicious code modifies your package.json file, removes private flags, and can lead to unauthorized republishing of your packages, compromising your project's integrity.

You can use Vulert, which monitors vulnerabilities in your package-lock.json file. Visit Vulert Scanner to check if your application is affected without needing to sign up.

If you find the unknown_snail_z3n package in your dependencies, you should uninstall it immediately using the command: npm uninstall unknown_snail_z3n.

There are no patches available for the unknown_snail_z3n package as it is recommended to remove it entirely from your project.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall unknown_snail_z3n

If 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 →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback