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

teagood-cuekin59 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-166826: Malicious code in teagood-cuekin59 (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 Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

teagood-cuekin59 is an npm package that is part of the tea.xyz token reward campaign, which has been associated with a series of malicious activities aimed at manipulating developer reputation scores. This package is designed to automatically generate and publish derivative packages with randomized names, thereby inflating the reputation of developers involved in the tea protocol token rewards. The malicious nature of this package poses significant risks to the integrity of the npm registry and the security of applications relying on it.

Vulnerability Detail

The vulnerability in teagood-cuekin59 originates from its design to execute autopublish scripts that modify the package.json file. These modifications include removing private flags, altering version numbers, and generating random package names, which leads to the continuous republishing of variants. This behavior not only pollutes the npm registry but also compromises the security of applications that may inadvertently depend on these malicious packages. The potential ramifications include unauthorized access to sensitive data, disruption of application functionality, and damage to developer reputations.

How To Fix

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

npm uninstall teagood-cuekin59

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 measure, you can avoid using the affected package by removing it from your project dependencies and replacing it with a trusted alternative. Additionally, consider using tools like Vulert to monitor your package-lock.json file for vulnerabilities in real-time.

Conclusion

The discovery of malicious code in teagood-cuekin59 highlights the importance of vigilance in managing npm packages. By understanding the nature of this vulnerability and taking proactive steps to mitigate risks, developers can protect their applications and maintain the integrity of the npm ecosystem.

See every vulnerability recorded for teagood-cuekin59 →

Share this vulnerability

FAQ

teagood-cuekin59 is an npm package associated with the tea.xyz token reward campaign, known for its malicious activities.

The vulnerability can lead to the injection of malicious code, compromising the security and functionality of your application.

You should uninstall the package immediately using 'npm uninstall teagood-cuekin59' and check your application for any potential impacts.

You can use tools like Vulert, which monitors your package-lock.json for vulnerabilities in real-time without requiring code access.

Yes, 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-cuekin59

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