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

teagood-cuekin10 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-166771: Malicious code in teagood-cuekin10 (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-cuekin10 is a package associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with numerous derivative packages. This package is designed to automate the generation and publication of these derivatives, often with randomized names, to inflate developer reputation scores for token rewards. Its functionality is compromised by the presence of malicious scripts that manipulate package metadata.

Vulnerability Detail

The vulnerability in teagood-cuekin10 originates from its inclusion in a campaign that utilizes autopublish scripts to create and publish numerous derivative packages. These scripts modify the package.json file by removing private flags, altering version numbers, and generating random package names. This behavior not only pollutes the npm registry but also poses a risk of unintentional dependency on malicious packages, potentially leading to security breaches in applications that rely on them.

How To Fix

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

npm uninstall teagood-cuekin10

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 affected package and look for alternative packages that provide similar functionality without the associated risks. Ensure that your package-lock.json is monitored for any dependencies that may include this malicious package.

Conclusion

The presence of malicious code in the teagood-cuekin10 package poses a significant risk to the npm ecosystem. It is crucial for developers to be vigilant about the packages they include in their projects and to utilize monitoring tools like Vulert to stay informed about potential vulnerabilities.

See every vulnerability recorded for teagood-cuekin10 →

Share this vulnerability

FAQ

teagood-cuekin10 is an npm package linked to the tea.xyz token reward campaign, known for flooding the npm registry with derivative packages.

The vulnerability can lead to the inclusion of malicious code in your application, potentially compromising its security and functionality.

You should uninstall the package immediately and monitor your project for any dependencies that may include it.

You can use tools like Vulert, which monitors your package-lock.json 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 any signup.

How To Fix

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

npm uninstall teagood-cuekin10

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