Malicious Code Injection in teagood-yakuna96: A Threat to npm Users

teagood-yakuna96 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-167960: Malicious code in teagood-yakuna96 (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-yakuna96 is an npm package that is part of the tea.xyz token reward campaign. This package is designed to interact with the npm registry, allowing developers to publish and manage JavaScript packages. However, it has been identified as malicious, containing scripts that automatically generate and publish derivative packages with altered metadata, which can lead to reputation inflation and registry pollution.

Vulnerability Detail

The vulnerability in teagood-yakuna96 originates from its inclusion in a campaign that floods the npm registry with malicious packages. The package contains scripts that modify the package.json file to remove private flags, change version numbers, and generate random package names. This behavior not only compromises the integrity of the npm registry but also poses a risk to developers who may unknowingly install these malicious packages, leading to potential security breaches and loss of trust in the ecosystem.

How To Fix

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

npm uninstall teagood-yakuna96

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 measure, you can avoid using the affected package by removing it from your project and replacing it with a trusted alternative. Ensure that you audit your package-lock.json file for any other potentially malicious packages.

Conclusion

The discovery of malicious code in the teagood-yakuna96 package highlights the importance of vigilance in managing dependencies within the npm ecosystem. By understanding the nature of this vulnerability and taking proactive steps to mitigate risks, developers can protect their projects and maintain the integrity of their software environments.

See every vulnerability recorded for teagood-yakuna96 →

Share this vulnerability

FAQ

teagood-yakuna96 is an npm package that is part of a malicious campaign aimed at inflating developer reputation scores through the publication of derivative packages.

The vulnerability can lead to the installation of malicious packages that compromise your project's security and integrity, potentially allowing unauthorized access or data breaches.

If you have installed teagood-yakuna96, you should uninstall it immediately using 'npm uninstall teagood-yakuna96' and audit your project for any other malicious dependencies.

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 without needing to sign up.

Yes, consider using well-established and trusted packages that provide similar functionality without the associated risks of malicious behavior.

How To Fix

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

npm uninstall teagood-yakuna96

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