Malicious Code Injection in rich_mouse-smiletea Package

rich_mouse-smiletea Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-108055: Malicious code in rich_mouse-smiletea (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 rich_mouse-smiletea 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 are often used to inflate developer reputation scores for token rewards. However, it has been identified as containing malicious code that compromises its integrity and the security of applications that utilize it.

Vulnerability Detail

The vulnerability in the rich_mouse-smiletea package stems from its inclusion in a campaign that floods the npm registry with malicious packages. The malicious code modifies the package.json file to remove private flags, alters version numbers, and generates random package names, leading to potential pollution of the npm registry. This can result in developers inadvertently using compromised packages, which may expose their applications to security risks such as unauthorized access or data breaches.

How To Fix

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

npm uninstall rich_mouse-smiletea

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 rich_mouse-smiletea package and look for alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your package dependencies using tools like Vulert, which can alert you to vulnerabilities in real-time without requiring code access.

Conclusion

The rich_mouse-smiletea package has been identified as containing malicious code that poses a significant risk to applications using it. It is crucial to remove this package and monitor your dependencies for vulnerabilities to maintain the security of your software.

See every vulnerability recorded for rich_mouse-smiletea →

Share this vulnerability

FAQ

The rich_mouse-smiletea package is an npm package associated with the tea.xyz token reward campaign, designed to automate the publication of derivative packages.

The vulnerability can lead to the use of compromised packages, which may expose your application to security risks such as unauthorized access or data breaches.

You should uninstall the rich_mouse-smiletea package immediately using 'npm uninstall rich_mouse-smiletea' and check for any alternative packages.

Yes, you can use Vulert to monitor your package-lock.json file for vulnerabilities in real-time without needing access to the code.

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

How To Fix

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

npm uninstall rich_mouse-smiletea

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