Malicious Code Injection in teagood-yakuza7: npm Package Vulnerability

teagood-yakuza7 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-168030: Malicious code in teagood-yakuza7 (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-yakuza7 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 containing malicious code that compromises its integrity and the npm registry.

Vulnerability Detail

The vulnerability originates from the malicious code embedded within the teagood-yakuza7 package. This code includes autopublish scripts that modify the package.json file by removing private flags, altering version numbers, and generating random package names. The continuous republishing of these variants can lead to pollution of the npm registry, potentially harming developers' reputations and the integrity of the ecosystem.

How To Fix

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

npm uninstall teagood-yakuza7

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 prevent the installation of the affected package by using npm's package-lock.json to lock your dependencies. Additionally, you can monitor your project for vulnerabilities using tools like Vulert, which can alert you to any open-source vulnerabilities in real-time.

Conclusion

The teagood-yakuza7 npm package contains malicious code that poses a significant risk to developers and the integrity of the npm registry. It is crucial to remove this package and monitor for vulnerabilities using tools like Vulert to ensure the security of your applications.

See every vulnerability recorded for teagood-yakuza7 →

Share this vulnerability

FAQ

The malicious code can lead to the pollution of the npm registry, affecting the reputation of developers and potentially compromising the security of applications that depend on this package.

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

If you have installed teagood-yakuza7, it is advisable to remove it from your project immediately and monitor for any updates or patches.

Yes, Vulert can monitor your package-lock.json file to alert you in real-time for any open-source vulnerabilities in your software.

Failing to address this vulnerability could lead to security breaches, loss of developer reputation, and potential exploitation of your application by malicious actors.

How To Fix

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

npm uninstall teagood-yakuza7

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