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

teagood-cuekin75 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-166843: Malicious code in teagood-cuekin75 (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-cuekin75 is a package within the npm ecosystem, part of a broader campaign associated with the tea.xyz token reward initiative. This package is designed to manipulate the npm registry by generating and publishing numerous derivative packages with randomized names, aiming to inflate developer reputation scores for token rewards. Its functionality is compromised due to the presence of malicious scripts that alter package metadata.

Vulnerability Detail

The vulnerability in teagood-cuekin75 originates from its association with the tea.xyz token reward campaign, which has led to the introduction of malicious code. This code modifies the package.json file by removing private flags, changing version numbers, and generating random package names. The continuous republishing of these variants pollutes the npm registry, potentially leading to security risks for developers who unknowingly depend on these compromised packages.

How To Fix

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

npm uninstall teagood-cuekin75

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 and replacing it with a trusted alternative. 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 discovery of malicious code in teagood-cuekin75 highlights the importance of vigilance in the npm ecosystem. Developers should take immediate action to remove the affected package and utilize tools like Vulert to monitor their projects for vulnerabilities. Staying informed and proactive can help mitigate risks associated with open-source dependencies.

See every vulnerability recorded for teagood-cuekin75 →

Share this vulnerability

FAQ

teagood-cuekin75 is an npm package that has been identified as malicious due to its involvement in a token reward campaign that manipulates the npm registry.

The vulnerability can lead to the introduction of malicious code into your project, potentially compromising its security and integrity.

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

Yes, tools like Vulert can monitor your project for open-source vulnerabilities in real-time, using just your package-lock.json.

You can check if your application is affected by this vulnerability using the Vulert playground at Vulert Scanner 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-cuekin75

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