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

teagood-cuekin70 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-166838: Malicious code in teagood-cuekin70 (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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

teagood-cuekin70 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 the automatic generation and publication of derivative packages. However, it has been identified as containing malicious code that compromises its integrity and the security of the npm ecosystem.

Vulnerability Detail

The vulnerability in teagood-cuekin70 originates from its design to include autopublish scripts that modify the package.json file. These modifications remove private flags, alter version numbers, and generate random package names, leading to the pollution of the npm registry with potentially harmful packages. The malicious payload can significantly impact developers by inflating reputation scores fraudulently and compromising the integrity of the npm ecosystem.

How To Fix

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

npm uninstall teagood-cuekin70

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 remove the affected package from your project by executing: npm uninstall teagood-cuekin70. This will prevent any malicious code from executing until a secure version is available.

Conclusion

The teagood-cuekin70 package poses a significant risk due to its malicious code that modifies package.json and publishes harmful variants. It is crucial for developers to take immediate action by uninstalling the package and monitoring their projects for vulnerabilities.

See every vulnerability recorded for teagood-cuekin70 →

Share this vulnerability

FAQ

teagood-cuekin70 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 and compromise the integrity of your project by introducing malicious code.

You should uninstall the package immediately and check for any updates or patches that may address the vulnerability.

Yes, you can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities 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 any signup.

How To Fix

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

npm uninstall teagood-cuekin70

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