Malicious Code Vulnerability in previous_snail_0xrequest Package

previous_snail_0xrequest Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-107249: Malicious code in previous_snail_0xrequest (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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The previous_snail_0xrequest 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. However, it has been compromised to include malicious scripts that can alter package metadata and republish variants, leading to potential abuse within the npm registry.

Vulnerability Detail

The vulnerability originates from the malicious code embedded in the previous_snail_0xrequest package. This code modifies the package.json file by removing private flags, changing version numbers, and generating random package names, which can lead to the pollution of the npm registry. The malicious payload is designed to continuously republish these variants, making it difficult for developers to maintain clean and secure package dependencies. The ramifications include compromised project integrity, potential security risks, and damage to developer reputation.

How To Fix

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

npm uninstall previous_snail_0xrequest

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 remove the previous_snail_0xrequest package from your project by running: npm uninstall previous_snail_0xrequest. This will prevent any malicious code from executing until a safe version is available.

Conclusion

The previous_snail_0xrequest package has been identified as containing malicious code that can compromise project integrity and security. It is crucial for developers to update or remove this package to safeguard their applications. Utilizing tools like Vulert can help monitor for such vulnerabilities in real-time.

See every vulnerability recorded for previous_snail_0xrequest →

Share this vulnerability

FAQ

It is an npm package associated with the tea.xyz token reward campaign, designed to generate and publish derivative packages.

The malicious code can alter your package.json file, remove private flags, and republish variants, leading to potential security risks and project integrity issues.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without requiring any signup.

As a workaround, you can uninstall the previous_snail_0xrequest package to prevent any malicious code from executing.

Detailed information can be found in the vulnerability report and on the Vulert platform, which provides insights into open-source vulnerabilities.

How To Fix

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

npm uninstall previous_snail_0xrequest

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