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

teagood-cuekin78 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-166846: Malicious code in teagood-cuekin78 (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-cuekin78 is an npm package that is part of the tea.xyz token reward campaign. This package is designed to interact with the npm registry, potentially inflating developer reputation scores through automated publishing. It is characterized by its ability to generate and publish derivative packages with randomized names, which can lead to pollution of the npm registry and compromise the integrity of the ecosystem.

Vulnerability Detail

The vulnerability in teagood-cuekin78 stems from its malicious payload that modifies the package.json file. It removes private flags, alters version numbers, and generates random package names, which are often themed around Indonesian culture. This behavior is intended to create numerous derivative packages that clutter the npm registry, making it difficult for developers to find legitimate packages. The origin of this issue is linked to the tea.xyz token reward campaign, which incentivizes such practices.

How To Fix

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

npm uninstall teagood-cuekin78

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 by removing it from your dependencies. 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-cuekin78 package poses a significant risk to the npm ecosystem due to its malicious behavior of generating and publishing derivative packages. It is crucial for developers to remove this package from their projects and utilize tools like Vulert to stay informed about vulnerabilities in their dependencies.

See every vulnerability recorded for teagood-cuekin78 →

Share this vulnerability

FAQ

teagood-cuekin78 is an npm package associated with the tea.xyz token reward campaign, designed to publish derivative packages automatically.

The vulnerability can lead to the pollution of the npm registry, making it harder to find legitimate packages and potentially compromising your project's integrity.

You should uninstall the package immediately using the command npm uninstall teagood-cuekin78 and monitor your project for any further vulnerabilities.

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

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-cuekin78

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