Malicious Code in teagood-yakuna51: A Threat to npm Ecosystem

teagood-yakuna51 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

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

teagood-yakuna51 is an npm package that is part of the tea.xyz token reward campaign. This package is designed to interact with the npm registry and is involved in generating and publishing derivative packages. Its primary functionality revolves around automating the publication process, but it has been compromised to include malicious scripts that can harm the integrity of the npm ecosystem.

Vulnerability Detail

The vulnerability in teagood-yakuna51 originates from its inclusion in a campaign that floods the npm registry with malicious packages. These packages contain scripts that modify the package.json file to remove private flags, alter version numbers, and generate random package names. This behavior leads to the pollution of the npm registry, potentially affecting developers' reputations and the overall trustworthiness of the ecosystem.

How To Fix

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

npm uninstall teagood-yakuna51

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-yakuna51 package and any other packages that are part of the tea.xyz token reward campaign. Monitor your package-lock.json file for any unauthorized changes and remove any suspicious packages immediately.

Conclusion

The discovery of malicious code in the teagood-yakuna51 npm package highlights the importance of vigilance in managing dependencies. By understanding the nature of this vulnerability and taking appropriate actions, developers can protect their projects and maintain the integrity of the npm ecosystem.

See every vulnerability recorded for teagood-yakuna51 →

Share this vulnerability

FAQ

teagood-yakuna51 is an npm package associated with the tea.xyz token reward campaign, which has been found to contain malicious code.

The malicious code modifies your package.json file, removes private flags, and generates random package names, which can lead to the pollution of the npm registry and damage your project's reputation.

You should uninstall the package immediately using 'npm uninstall teagood-yakuna51' and check your project for any unauthorized changes.

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

Currently, there is no patch for teagood-yakuna51 as it is recommended to remove the package entirely from your project.

How To Fix

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

npm uninstall teagood-yakuna51

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