Malicious Code Injection in teagood-cuekin66: npm Package Vulnerability

teagood-cuekin66 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-166833: Malicious code in teagood-cuekin66 (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 package teagood-cuekin66 is part of a series of npm packages associated with the tea.xyz token reward campaign. These packages are designed to inflate developer reputation scores through the automatic generation and publication of derivative packages with randomized names. This behavior is indicative of a broader issue within the npm ecosystem, where malicious actors exploit the platform for personal gain.

Vulnerability Detail

The vulnerability in teagood-cuekin66 stems from its malicious payload, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This allows the package to continuously republish variants, polluting the npm registry and potentially compromising the integrity of other packages. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which has been known to flood npm with similar malicious packages.

How To Fix

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

npm uninstall teagood-cuekin66

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 installation of this package by using npm's package-lock.json to lock your dependencies. Additionally, consider using the following command to uninstall the package: npm uninstall teagood-cuekin66.

Conclusion

The teagood-cuekin66 package poses a significant risk due to its malicious code that alters package metadata and floods the npm registry. It is crucial for developers to remain vigilant and take immediate action to remove such packages from their projects. Utilizing tools like Vulert can help in monitoring and managing vulnerabilities effectively.

See every vulnerability recorded for teagood-cuekin66 →

Share this vulnerability

FAQ

teagood-cuekin66 is an npm package associated with the tea.xyz token reward campaign, designed to inflate developer reputation scores.

The vulnerability can lead to the pollution of the npm registry and compromise the integrity of your project's dependencies.

You should uninstall the package immediately and monitor for any updates or patches from the package maintainers.

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

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected without any signup.

How To Fix

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

npm uninstall teagood-cuekin66

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