Malicious Code Injection in Grateful Deer-Smiletea Package

grateful_deer-smiletea Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-103351: Malicious code in grateful_deer-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 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 'grateful_deer-smiletea' package is part of the tea.xyz token reward campaign that has infiltrated the npm ecosystem. This package is designed to facilitate token rewards by generating and publishing derivative packages with randomized names. Its functionality is compromised by malicious scripts that manipulate package metadata, leading to potential security risks.

Vulnerability Detail

The vulnerability originates from the presence of malicious code within the 'grateful_deer-smiletea' package. This code is designed to automatically modify the package.json file, removing private flags, altering version numbers, and generating random package names. The malicious payload continuously republishes these variants, polluting the npm registry and potentially leading to reputation inflation for developers involved in the tea protocol token rewards. The ramifications include compromised package integrity, increased risk of dependency confusion, and potential exploitation of affected systems.

How To Fix

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

npm uninstall grateful_deer-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 prevent the execution of the malicious scripts by removing the package and avoiding any installations from unverified sources. Additionally, consider using a package-lock.json file to lock your dependencies and prevent unwanted changes.

Conclusion

The 'grateful_deer-smiletea' package poses a significant security risk due to its malicious code that alters package metadata and repurposes it for unauthorized use. It is crucial to remove this package and monitor your dependencies to maintain the integrity of your projects.

See every vulnerability recorded for grateful_deer-smiletea →

Share this vulnerability

FAQ

It is a package associated with the tea.xyz token reward campaign that has been identified to contain malicious code.

The malicious code modifies your package.json file and can lead to the publication of unauthorized packages, compromising your project's integrity.

You should uninstall the package immediately using 'npm uninstall grateful_deer-smiletea' and check for any unauthorized changes in your project.

Yes, you can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities using just your package-lock.json file.

You can use the Vulert playground at Vulert Scanner to check if your application is affected without needing to sign up.

How To Fix

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

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