Malicious Code Injection in assistant_snail_z3n: npm Package Vulnerability

assistant_snail_z3n Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-93290: Malicious code in assistant_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 Devnack Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The assistant_snail_z3n package is part of the npm ecosystem, often used in JavaScript applications. It is associated with the tea.xyz token reward campaign, which has been linked to a series of malicious packages flooding the npm registry. This package is designed to inflate developer reputation scores through automated publishing scripts.

Vulnerability Detail

The vulnerability in the assistant_snail_z3n package stems from its malicious code that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior is intended to pollute the npm registry by continuously republishing variants, which can lead to security risks and reputation damage for developers. The origin of this vulnerability is traced back to the package's association with the tea.xyz token reward campaign, which employs autopublish scripts to exploit the npm ecosystem.

How To Fix

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

npm uninstall assistant_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 an immediate workaround, you can remove the assistant_snail_z3n package from your project by executing the following command: npm uninstall assistant_snail_z3n. This will prevent any malicious code from executing in your application.

Conclusion

The assistant_snail_z3n package contains a significant vulnerability due to its malicious code that modifies essential files and repopulates the npm registry with harmful variants. It is essential for developers to take immediate action by updating or removing the package to safeguard their applications.

See every vulnerability recorded for assistant_snail_z3n →

Share this vulnerability

FAQ

The assistant_snail_z3n package is an npm package associated with the tea.xyz token reward campaign, which has been linked to malicious activities in the npm registry.

The vulnerability can lead to unauthorized modifications of your package.json file, potentially compromising your application's integrity and security.

If you are using the assistant_snail_z3n package, it is crucial to update to a patched version or remove the package entirely to mitigate the risk.

You can use tools like Vulert, which monitors your package-lock.json file to alert you in real-time for open-source vulnerabilities. You can also check your application against vulnerabilities using the Vulert playground.

Detailed information about this vulnerability can be found in the Open Source Vulnerability database and through security advisories related to the npm ecosystem.

How To Fix

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

npm uninstall assistant_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