Malicious Code Injection in teagood-yakuna41 Package

teagood-yakuna41 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-167900: Malicious code in teagood-yakuna41 (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 Penetration testing for web, API and mobile 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-yakuna41 package is part of the tea.xyz token reward campaign, which has been known to flood the npm ecosystem with numerous packages. These packages typically include scripts that automatically generate and publish derivative packages with randomized names, aimed at inflating developer reputation scores for token rewards. The package's functionality is compromised by malicious code that alters its metadata.

Vulnerability Detail

The vulnerability in the teagood-yakuna41 package originates from its association with a malicious campaign that modifies the package.json file. This modification removes private flags, changes version numbers, and generates random package names, leading to the continuous republishing of these variants. The ramifications include pollution of the npm registry and potential security risks for developers who inadvertently use these compromised packages.

How To Fix

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

npm uninstall teagood-yakuna41

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-yakuna41 package from your project by executing the following command: npm uninstall teagood-yakuna41. This will prevent any malicious code from executing in your environment until a safe version is available.

Conclusion

The teagood-yakuna41 package contains a significant vulnerability due to its malicious code that alters package metadata. It is crucial for developers to take immediate action by updating or removing the package to safeguard their projects from potential risks.

See every vulnerability recorded for teagood-yakuna41 →

Share this vulnerability

FAQ

teagood-yakuna41 is a package associated with the tea.xyz token reward campaign, which aims to inflate developer reputation scores through the publication of numerous derivative packages.

The vulnerability can lead to the pollution of the npm registry and may introduce security risks if your project relies on compromised packages.

You can use Vulert to monitor and alert for open-source vulnerabilities in your software. Visit Vulert Scanner to check if your application is affected without requiring any signup.

If you cannot update the package, consider removing it from your project as a temporary measure until a safe version is released.

More information can be found in the official npm registry or by checking the GitHub repository for the package.

How To Fix

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

npm uninstall teagood-yakuna41

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