Malicious Code Injection in cloudy_hamster-smiletea Package

cloudy_hamster-smiletea Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-100617: Malicious code in cloudy_hamster-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 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 cloudy_hamster-smiletea package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. It is designed to facilitate the generation and publication of derivative packages. However, this package has been identified as malicious, containing scripts that manipulate package metadata and flood the npm registry with unwanted variants.

Vulnerability Detail

The vulnerability originates from the malicious design of the cloudy_hamster-smiletea package, which includes autopublish scripts that modify the package.json file. These modifications remove private flags, alter version numbers, and generate random package names, leading to the pollution of the npm registry. The potential ramifications include compromised developer reputation scores and the risk of unintentional dependency on malicious packages by other developers.

How To Fix

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

npm uninstall cloudy_hamster-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 cloudy_hamster-smiletea package and instead utilize alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your package-lock.json file for any unexpected changes.

Conclusion

The cloudy_hamster-smiletea package poses a significant risk due to its malicious code that alters package metadata and floods the npm registry. It is crucial to remove this package from your project and monitor for any updates or patches to safeguard your application.

See every vulnerability recorded for cloudy_hamster-smiletea →

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 modifies your package.json, potentially leading to the publication of unwanted packages and compromising your project's integrity.

You should remove the cloudy_hamster-smiletea package from your project and monitor for any updates or patches.

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

Yes, you can use the Vulert playground at Vulert Scanner to check for vulnerabilities in your application without any signup.

How To Fix

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

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