Malicious Code Injection in teagood-yakuna55: npm Package Vulnerability

teagood-yakuna55 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-167915: Malicious code in teagood-yakuna55 (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-yakuna55 is an npm package that is part of the tea.xyz token reward campaign, which has been known to flood the npm registry with various packages. These packages are designed to inflate developer reputation scores through automated scripts that generate and publish derivative packages with randomized names. The package's functionality is compromised due to malicious code that alters its configuration and behavior.

Vulnerability Detail

The vulnerability in teagood-yakuna55 originates from its inclusion in a campaign that employs autopublish scripts to create and publish numerous derivative packages. This malicious payload modifies the package.json file by removing private flags, changing version numbers, and generating random package names. As a result, it pollutes the npm registry and can lead to 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-yakuna55

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 workaround, you can avoid using the teagood-yakuna55 package altogether. If it is already included in your project, consider removing it and replacing it with a trusted alternative. Additionally, you can monitor your dependencies using tools like Vulert, which can alert you to vulnerabilities in real-time without requiring code access.

Conclusion

The teagood-yakuna55 package contains malicious code that compromises its integrity and can lead to security vulnerabilities in projects that use it. It is crucial to remove this package and monitor your dependencies for any potential threats. Utilizing tools like Vulert can help you stay informed about vulnerabilities in your open-source software.

See every vulnerability recorded for teagood-yakuna55 →

Share this vulnerability

FAQ

teagood-yakuna55 is an npm package involved in a token reward campaign that generates numerous derivative packages to inflate developer reputation scores.

The malicious code modifies your package.json file, removes private flags, and generates random package names, which can lead to security vulnerabilities and pollution of the npm registry.

You should remove the teagood-yakuna55 package from your project and monitor for any updates or patches that may address the vulnerability.

You can use tools like Vulert, which monitors your package-lock.json file to alert you in real-time for open-source vulnerabilities without requiring code access.

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.

How To Fix

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

npm uninstall teagood-yakuna55

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