Malicious Code Injection in teagood-cuekin5: A Threat to npm Ecosystem

teagood-cuekin5 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-166816: Malicious code in teagood-cuekin5 (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

teagood-cuekin5 is an npm package that is part of the tea.xyz token reward campaign. This package is designed to interact with the npm registry and is often used by developers to manage dependencies in their JavaScript applications. However, it has been identified as malicious due to its involvement in generating and publishing derivative packages with the intent to inflate developer reputation scores for token rewards.

Vulnerability Detail

The vulnerability in teagood-cuekin5 originates from its malicious payload, which modifies the package.json file by removing private flags and altering version numbers. It generates random package names, often themed around Indonesian culture, and continuously republishes these variants to pollute the npm registry. This behavior not only compromises the integrity of the npm ecosystem but also poses a risk to developers who may unknowingly install these malicious packages.

How To Fix

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

npm uninstall teagood-cuekin5

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 teagood-cuekin5 package and look for alternative packages that provide similar functionality without the associated risks. Additionally, you can utilize tools like Vulert to monitor your package-lock.json file for vulnerabilities in real-time.

Conclusion

The teagood-cuekin5 package poses a significant threat to the npm ecosystem due to its malicious behavior. It is crucial for developers to be vigilant, remove affected packages, and utilize tools like Vulert to monitor for vulnerabilities. Staying informed and proactive can help maintain the security of your applications.

See every vulnerability recorded for teagood-cuekin5 →

Share this vulnerability

FAQ

teagood-cuekin5 is an npm package associated with the tea.xyz token reward campaign, which has been identified as malicious.

The vulnerability can lead to the installation of malicious packages that may compromise your application's integrity and security.

You should uninstall the package immediately using 'npm uninstall teagood-cuekin5' and check for any other affected packages.

You can use Vulert, which monitors your package-lock.json file for vulnerabilities in real-time 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 signing up.

How To Fix

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

npm uninstall teagood-cuekin5

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