Malicious Code Injection in teagood-yakuna94: A Threat to npm Users

teagood-yakuna94 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-167958: Malicious code in teagood-yakuna94 (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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

teagood-yakuna94 is a package within the npm ecosystem, often associated with the tea.xyz token reward campaign. This package is designed to facilitate token rewards through automatic publishing scripts. However, it has been identified as malicious, containing scripts that manipulate package metadata and flood the npm registry with derivative packages.

Vulnerability Detail

The vulnerability in teagood-yakuna94 originates from its inclusion in a campaign that aims to inflate developer reputation scores for token rewards. The malicious code modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior not only compromises the integrity of the npm registry but also poses risks to developers who may unknowingly use these compromised packages, leading to potential security breaches in their applications.

How To Fix

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

npm uninstall teagood-yakuna94

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-yakuna94 package and look for alternative packages that provide similar functionality without the associated risks. Always verify the integrity and reputation of packages before including them in your project.

Conclusion

The discovery of malicious code in the teagood-yakuna94 package highlights the importance of vigilance when using open-source packages. Developers should take proactive measures to secure their applications by regularly auditing their dependencies and utilizing tools like Vulert for real-time vulnerability monitoring.

See every vulnerability recorded for teagood-yakuna94 →

Share this vulnerability

FAQ

teagood-yakuna94 is an npm package associated with the tea.xyz token reward campaign, which has been identified as malicious.

The malicious code can modify your package.json file, remove private flags, and flood the npm registry with compromised packages, potentially leading to security vulnerabilities in your application.

If you have installed teagood-yakuna94, you should uninstall it immediately using 'npm uninstall teagood-yakuna94' and review your project for any other potentially compromised packages.

You can use tools like Vulert, which monitors your package-lock.json file for open-source vulnerabilities in real-time. You can check your application for vulnerabilities using the Vulert playground without any signup.

Yes, you should look for alternative packages that provide similar functionality but have a good reputation and are actively maintained. Always check the package's reviews and security history.

How To Fix

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

npm uninstall teagood-yakuna94

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