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

teagood-cuekin15 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-166778: Malicious code in teagood-cuekin15 (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-cuekin15 is an npm package that is part of the tea.xyz token reward campaign, which has been associated with the proliferation of malicious packages in the npm registry. These packages are designed to inflate developer reputation scores by automatically generating and publishing derivative packages with randomized names. The presence of malicious code in this package poses a significant risk to developers and users relying on npm for package management.

Vulnerability Detail

The vulnerability in teagood-cuekin15 originates from its design to include autopublish scripts that modify the package.json file. This malicious payload removes private flags, alters version numbers, and generates random package names, leading to the continuous republishing of variants that pollute the npm registry. The ramifications include potential security breaches, loss of developer reputation, and the risk of users inadvertently installing compromised packages.

How To Fix

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

npm uninstall teagood-cuekin15

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

Conclusion

The presence of malicious code in the teagood-cuekin15 npm package poses a significant threat to developers and users. It is crucial to stay informed about such vulnerabilities and take immediate action to mitigate risks. Regularly updating packages and utilizing monitoring tools like Vulert can help maintain the security of your applications.

See every vulnerability recorded for teagood-cuekin15 →

Share this vulnerability

FAQ

teagood-cuekin15 is an npm package associated with the tea.xyz token reward campaign, known for containing malicious code.

The malicious code modifies your package.json, removes private flags, and can lead to the installation of compromised packages, affecting your project's security.

You should uninstall the package immediately and check for any updates or patches before reinstalling.

You can use tools like Vulert, which monitors your package-lock.json for open-source vulnerabilities in real-time without requiring code access.

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without signing up.

How To Fix

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

npm uninstall teagood-cuekin15

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