Malicious Code Exploit in rear_snail-appteadev Package: npm Vulnerability Overview

rear_snail-appteadev Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-107780: Malicious code in rear_snail-appteadev (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 rear_snail-appteadev package is part of the npm ecosystem, primarily used for developing applications with JavaScript. This package has been identified as part of a malicious campaign that aims to exploit npm's package management system. It is designed to automatically generate and publish derivative packages, which can lead to reputation inflation for developers involved in the tea.xyz token reward scheme. The presence of this package poses significant risks to developers and users alike, as it can compromise the integrity of the npm registry.

Vulnerability Detail

The vulnerability originates from the malicious intent behind the rear_snail-appteadev package, which includes scripts that modify the package.json file to remove private flags and change version numbers. It generates random package names, often themed around Indonesian culture, and continuously republishes variants to pollute the npm registry. This behavior can lead to the proliferation of insecure packages, potentially allowing attackers to exploit unsuspecting developers who may inadvertently use these compromised packages in their applications.

How To Fix

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

npm uninstall rear_snail-appteadev

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 workaround, ensure that your project does not include the rear_snail-appteadev package. Regularly audit your package dependencies using tools like npm audit to identify and address any vulnerabilities in your project.

Conclusion

The rear_snail-appteadev package poses a significant security risk due to its malicious behavior of modifying package metadata and republishing insecure variants. It is crucial for developers to remove this package from their projects and utilize tools like Vulert to monitor for vulnerabilities in their dependencies.

See every vulnerability recorded for rear_snail-appteadev →

Share this vulnerability

FAQ

The rear_snail-appteadev package is an npm package that has been identified as part of a malicious campaign aimed at exploiting the npm registry.

This vulnerability can lead to the introduction of insecure packages into your application, potentially compromising its security and integrity.

You should immediately uninstall the rear_snail-appteadev package from your project to prevent any potential security risks.

You can use tools like Vulert, which monitors and alerts for open-source vulnerabilities in your software without requiring code access or installation.

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.

How To Fix

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

npm uninstall rear_snail-appteadev

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