Malicious Code Injection in teagood-yakuna1 Package - npm Vulnerability

teagood-yakuna1 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

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

The teagood-yakuna1 package is part of the tea.xyz token reward campaign that has recently flooded the npm ecosystem. This package is designed to facilitate token rewards for developers by generating and publishing derivative packages. However, it has been identified as containing malicious scripts that compromise the integrity of the npm registry.

Vulnerability Detail

The vulnerability in the teagood-yakuna1 package originates from malicious code that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior is intended to inflate developer reputation scores by continuously republishing variants, thereby polluting the npm registry. The ramifications include potential security risks for developers who unknowingly use these compromised packages, as well as a degradation of the npm ecosystem's reliability.

How To Fix

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

npm uninstall teagood-yakuna1

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

Conclusion

The teagood-yakuna1 package poses a significant risk due to its malicious code that alters package metadata and floods the npm registry with compromised versions. It is crucial for developers to remain vigilant, update their dependencies, and utilize tools like Vulert to monitor for vulnerabilities in their applications.

See every vulnerability recorded for teagood-yakuna1 →

Share this vulnerability

FAQ

teagood-yakuna1 is an npm package associated with the tea.xyz token reward campaign, which aims to reward developers through token incentives.

The vulnerability involves the package modifying its own package.json file to remove private flags and generate random package names, leading to potential misuse and pollution of the npm registry.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. Visit Vulert Scanner to check if your application is affected without needing to sign up.

If you cannot update the package, it is advisable to uninstall it temporarily to mitigate any risks associated with the malicious code.

Detailed information can be found in the vulnerability report on the GitHub repository for malicious packages or through security advisories related to npm packages.

How To Fix

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

npm uninstall teagood-yakuna1

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