Malicious Code Injection in teagood-cuekin7 Package - npm Vulnerability

teagood-cuekin7 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

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

The teagood-cuekin7 package is part of a series of npm packages associated with the tea.xyz token reward campaign. These packages are designed to automate the generation and publication of derivative packages, often with randomized names, to inflate developer reputation scores for token rewards. This behavior poses a significant risk to the integrity of the npm registry and the security of applications relying on these packages.

Vulnerability Detail

The vulnerability originates from the malicious code embedded within the teagood-cuekin7 package. This code modifies the package.json file by removing private flags, altering version numbers, and generating random package names, which leads to the continuous republishing of these variants. The ramifications include the pollution of the npm registry, potential security risks for applications using these packages, and a compromised developer reputation system. The malicious payload is designed to exploit the npm ecosystem, making it crucial for developers to be vigilant.

How To Fix

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

npm uninstall teagood-cuekin7

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 workaround, you can monitor your package dependencies using tools like Vulert. By utilizing Vulert, you can check for vulnerabilities in your package-lock.json file without requiring access to the code or installation. You can also use the Vulert playground at https://vulert.com/scanner to check if your application is affected by this vulnerability without any signup.

Conclusion

The teagood-cuekin7 package poses a significant risk due to its malicious code that alters package configurations and floods the npm registry. It is essential for developers to remove this package and monitor their dependencies to safeguard their applications from potential threats.

See every vulnerability recorded for teagood-cuekin7 →

Share this vulnerability

FAQ

teagood-cuekin7 is an npm package that is part of a campaign to inflate developer reputation scores through automated package generation.

The malicious code can modify your package.json file, remove private flags, and continuously republish variants, potentially compromising your application's integrity.

You can use the Vulert playground at Vulert Scanner to check your application for vulnerabilities without needing to sign up.

You should uninstall the teagood-cuekin7 package immediately using the command npm uninstall teagood-cuekin7.

Regularly update your dependencies, use trusted packages, and monitor your package-lock.json file for vulnerabilities using tools like Vulert.

How To Fix

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

npm uninstall teagood-cuekin7

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