Malicious Code Injection in teagood-cuekin54: A Threat to npm Users

teagood-cuekin54 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

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

teagood-cuekin54 is an npm package that is part of the tea.xyz token reward campaign. This package is designed to facilitate the distribution of token rewards through various npm packages. However, it has been identified as malicious, containing scripts that automatically generate and publish derivative packages with randomized names, aimed at inflating developer reputation scores for the tea protocol.

Vulnerability Detail

The vulnerability in teagood-cuekin54 originates from its malicious payload, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior leads to the continuous republishing of variants, polluting the npm registry and potentially compromising the integrity of other packages. The malicious scripts included in the package (auto.js, autopublish.js, etc.) are specifically designed to automate this harmful process.

How To Fix

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

npm uninstall teagood-cuekin54

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 monitor your project for any signs of malicious behavior. Additionally, consider using tools like Vulert to monitor your package-lock.json for vulnerabilities in real-time. You can access Vulert's playground at https://vulert.com/scanner to check if your application is affected by this vulnerability without requiring any signup.

Conclusion

The discovery of malicious code in the teagood-cuekin54 package highlights the importance of vigilance when managing npm packages. By understanding the nature of this vulnerability and taking proactive steps to secure your projects, you can mitigate risks associated with malicious packages.

See every vulnerability recorded for teagood-cuekin54 →

Share this vulnerability

FAQ

teagood-cuekin54 is an npm package linked to the tea.xyz token reward campaign, which has been identified as containing malicious code.

The malicious code modifies package.json files, removes private flags, and generates random package names, leading to the pollution of the npm registry.

You can use tools like Vulert to monitor your package-lock.json for vulnerabilities and check if your application is affected.

You should uninstall the package immediately using npm uninstall teagood-cuekin54 and check for any other affected packages.

Regularly update your dependencies, monitor your projects with tools like Vulert, and review the packages you install for any known vulnerabilities.

How To Fix

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

npm uninstall teagood-cuekin54

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