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

teagood-cuekin83 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-166852: Malicious code in teagood-cuekin83 (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-cuekin83 is an npm package that is part of the tea.xyz token reward campaign. This package is designed to incentivize developers through token rewards by flooding the npm registry with derivative packages. It utilizes scripts that automatically generate and publish packages with randomized names, which can lead to reputation inflation for developers involved in the campaign. However, this behavior also poses significant risks to the integrity of the npm ecosystem.

Vulnerability Detail

The vulnerability in teagood-cuekin83 stems from its malicious payload that modifies the package.json file by removing private flags and altering version numbers. It generates random Indonesian-themed package names and continuously republishes these variants, polluting the npm registry. This behavior not only compromises the security of the affected packages but also affects the overall trustworthiness of the npm ecosystem, potentially leading to the installation of harmful code by unsuspecting developers.

How To Fix

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

npm uninstall teagood-cuekin83

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 teagood-cuekin83 package and any other packages that are part of the tea.xyz token reward campaign. Instead, consider using alternative packages that provide similar functionality without the associated risks.

Conclusion

The discovery of malicious code in the teagood-cuekin83 package highlights the importance of vigilance in the npm ecosystem. Developers should take immediate action to remove affected packages and utilize tools like Vulert to monitor for vulnerabilities in their applications. Staying informed and proactive can help maintain the integrity of your software projects.

See every vulnerability recorded for teagood-cuekin83 →

Share this vulnerability

FAQ

teagood-cuekin83 is an npm package involved in a token reward campaign that generates and publishes numerous derivative packages to inflate developer reputation scores.

The vulnerability can lead to the installation of malicious code, which may compromise your application's security and integrity.

You should uninstall the package immediately using 'npm uninstall teagood-cuekin83' and review your project's dependencies for any other potentially harmful packages.

You can use tools like Vulert, which monitors and alerts for open-source vulnerabilities in real-time using just your package-lock.json file. You can check if your application is affected by visiting the Vulert playground.

Yes, you should look for alternative packages that offer similar functionality without the risks associated with the tea.xyz token reward campaign.

How To Fix

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

npm uninstall teagood-cuekin83

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