Malicious Code Injection in teagood-yakuna80: A Threat to npm Ecosystem

teagood-yakuna80 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

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

teagood-yakuna80 is an npm package that is part of the tea.xyz token reward campaign. This package is designed to facilitate token rewards for developers by 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 variants.

Vulnerability Detail

The vulnerability in teagood-yakuna80 originates from its malicious payload, which alters the package.json file by removing private flags and changing version numbers. It generates random package names, primarily themed around Indonesian culture, and continuously republishes these variants. This behavior not only inflates developer reputation scores but also pollutes the npm registry, making it difficult for legitimate packages to be found and used. The potential ramifications include compromised package integrity and increased security risks for developers relying on the npm ecosystem.

How To Fix

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

npm uninstall teagood-yakuna80

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-yakuna80 package and look for alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your project for vulnerabilities using tools like Vulert, which analyzes your package-lock.json file for open-source vulnerabilities in real-time.

Conclusion

The teagood-yakuna80 package poses a significant threat to the npm ecosystem due to its malicious behavior. Developers are advised to remove this package from their projects and monitor their dependencies for vulnerabilities using tools like Vulert. Staying informed and proactive is essential to maintaining the integrity of your software.

See every vulnerability recorded for teagood-yakuna80 →

Share this vulnerability

FAQ

teagood-yakuna80 is an npm package associated with the tea.xyz token reward campaign, designed to generate and publish derivative packages.

The package modifies package.json files, removes private flags, changes version numbers, and floods the npm registry with random package variants.

You can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.

You should uninstall the package immediately using npm uninstall teagood-yakuna80 and check your project for any lingering references.

Yes, Vulert can monitor and alert you in real-time for open-source vulnerabilities in your software by analyzing your package-lock.json.

How To Fix

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

npm uninstall teagood-yakuna80

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