Malicious Code Injection in teagood-yakuna92 Package

teagood-yakuna92 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-167956: Malicious code in teagood-yakuna92 (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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The teagood-yakuna92 package is part of the tea.xyz token reward campaign that has infiltrated the npm ecosystem. This package is designed to facilitate the automatic generation and publication of derivative packages, which are often used to inflate developer reputation scores for token rewards. The package's functionality includes creating random package names and modifying existing package configurations, making it susceptible to exploitation.

Vulnerability Detail

The vulnerability in the teagood-yakuna92 package stems from its inclusion in a malicious campaign that modifies the package.json file to remove private flags and change version numbers. This allows the package to continuously republish variants with randomized names, polluting the npm registry and potentially compromising the integrity of other packages. The malicious payload can lead to unintended consequences for developers who may unknowingly use these compromised packages in their projects.

How To Fix

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

npm uninstall teagood-yakuna92

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-yakuna92 package until a fix is released. Additionally, you can monitor your package-lock.json file for any changes that may indicate the presence of this malicious package. Using Vulert, you can check if your application is affected by this vulnerability without requiring access to the code or installation.

Conclusion

The teagood-yakuna92 package poses a significant risk due to its malicious code that modifies package configurations and republish variants. It is crucial for developers to take immediate action by updating or removing the package to safeguard their projects. Utilizing tools like Vulert can help in monitoring for such vulnerabilities effectively.

See every vulnerability recorded for teagood-yakuna92 →

Share this vulnerability

FAQ

teagood-yakuna92 is a package that is part of a malicious campaign to inflate developer reputation scores in the npm ecosystem.

The vulnerability can lead to the introduction of malicious code into your project, potentially compromising its security and integrity.

You should update the package to a patched version if available or remove it from your project to mitigate the risk.

You can use tools like Vulert to monitor your package-lock.json file for open-source vulnerabilities in real-time.

Yes, you can use the Vulert playground at Vulert Scanner to check for vulnerabilities without requiring any signup.

How To Fix

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

npm uninstall teagood-yakuna92

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