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

teagood-yakuna74 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-167936: Malicious code in teagood-yakuna74 (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-yakuna74 is an npm package that is part of the tea.xyz token reward campaign. This package is designed to interact with the npm ecosystem, primarily aimed at generating and publishing derivative packages. However, it has been identified as malicious due to its functionality that modifies package metadata and floods the npm registry with unwanted packages.

Vulnerability Detail

The vulnerability in teagood-yakuna74 originates from its malicious code that alters the package.json file by removing private flags, changing version numbers, and generating random package names. This behavior is intended to inflate developer reputation scores for token rewards while polluting the npm registry with numerous derivative packages. The implications of this vulnerability include potential misuse of developer accounts, loss of control over package management, and degradation of the npm ecosystem's integrity.

How To Fix

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

npm uninstall teagood-yakuna74

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-yakuna74 package from your project by executing: npm uninstall teagood-yakuna74. This will prevent the malicious code from executing in your environment until a patch is available.

Conclusion

The teagood-yakuna74 package poses a significant risk to npm users due to its malicious behavior. It is crucial to take immediate action by updating or removing the package and utilizing tools like Vulert to monitor for vulnerabilities in your projects.

See every vulnerability recorded for teagood-yakuna74 →

Share this vulnerability

FAQ

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

The malicious code modifies package.json files, removes private flags, and generates random package names to inflate developer reputation scores.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software using just package-lock.json. Visit Vulert Scanner to check your application without signup.

Using this package can lead to compromised developer accounts, uncontrolled package management, and pollution of the npm registry.

Regularly update your dependencies, monitor your package-lock.json with tools like Vulert, and review the packages you include in your project.

How To Fix

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

npm uninstall teagood-yakuna74

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