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

teagood-yakuna46 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-167905: Malicious code in teagood-yakuna46 (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-yakuna46 is an npm package that is part of a broader campaign involving the tea.xyz token reward system. This package is designed to inflate developer reputation scores by automatically generating and publishing derivative packages with randomized names. Its functionality is compromised by malicious scripts that manipulate package metadata, posing a significant risk to developers and the integrity of the npm registry.

Vulnerability Detail

The vulnerability in teagood-yakuna46 originates from its involvement in a malicious campaign that floods the npm registry with derivative packages. The malicious payload modifies the package.json file by removing private flags, altering version numbers, and generating random package names. This behavior not only pollutes the npm registry but also compromises the security of applications relying on this package, potentially leading to further exploitation.

How To Fix

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

npm uninstall teagood-yakuna46

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-yakuna46 package altogether and seek alternative packages that provide similar functionality without the associated risks.

Conclusion

The discovery of malicious code in teagood-yakuna46 highlights the importance of vigilance in managing npm packages. Developers should take immediate action to remove this package and consider using tools like Vulert to monitor for vulnerabilities in their projects.

See every vulnerability recorded for teagood-yakuna46 →

Share this vulnerability

FAQ

teagood-yakuna46 is an npm package involved in a malicious campaign aimed at inflating developer reputation scores through the automatic generation of derivative packages.

The malicious code modifies package metadata, potentially leading to the installation of compromised packages that can harm your application and its users.

You should uninstall the package immediately using 'npm uninstall teagood-yakuna46' and check for any other potentially affected packages.

You can use tools like Vulert, which monitors your package-lock.json file for open-source vulnerabilities in real-time. You can also check your application against known vulnerabilities using the Vulert playground.

Yes, you should look for other reputable npm packages that provide similar functionality without the risks associated with teagood-yakuna46.

How To Fix

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

npm uninstall teagood-yakuna46

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