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

teagood-cuekin101 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

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

teagood-cuekin101 is an npm package that is part of the tea.xyz token reward campaign. This package is designed to interact with the npm registry, but it has been identified as containing malicious code that can compromise the integrity of the registry and the developer's reputation. The package is known for generating and publishing derivative packages with randomized names, which can lead to a polluted npm ecosystem.

Vulnerability Detail

The vulnerability originates from the malicious code embedded within the teagood-cuekin101 package. This code modifies the package.json file to remove private flags, alters version numbers, and generates random Indonesian-themed package names. The primary risk is that it can inflate developer reputation scores fraudulently and pollute the npm registry with numerous derivative packages, making it difficult for legitimate packages to be found and used. The continuous republishing of these variants can lead to a significant degradation of the npm ecosystem's reliability.

How To Fix

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

npm uninstall teagood-cuekin101

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-cuekin101 package and any packages that depend on it. Additionally, consider using tools like Vulert to monitor your project for vulnerabilities. You can check if your application is affected by this vulnerability using the Vulert playground at https://vulert.com/scanner without any signup.

Conclusion

The teagood-cuekin101 package poses a significant threat to the npm ecosystem due to its malicious code that modifies package metadata and floods the registry with unwanted packages. It is crucial for developers to remove this package and monitor their projects for vulnerabilities to maintain the integrity of their applications.

See every vulnerability recorded for teagood-cuekin101 →

Share this vulnerability

FAQ

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

The malicious code can modify your package.json file, inflate developer reputation scores fraudulently, and pollute the npm registry with unwanted packages.

You should uninstall the package immediately using 'npm uninstall teagood-cuekin101' and check for any other dependencies that may be affected.

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

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

How To Fix

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

npm uninstall teagood-cuekin101

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