Malicious Code Injection in teagood-yakuza5: A Threat to npm Packages

teagood-yakuza5 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-168008: Malicious code in teagood-yakuza5 (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 Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

teagood-yakuza5 is an npm package that is part of the tea.xyz token reward campaign, which has been associated with a series of malicious activities on the npm registry. This package is designed to manipulate package metadata and publish derivative packages, potentially compromising the integrity of the npm ecosystem.

Vulnerability Detail

The vulnerability in teagood-yakuza5 stems from its inclusion in a campaign that floods the npm registry with malicious packages. It contains scripts that modify package.json files to remove private flags, change version numbers, and generate random package names. This behavior can lead to the pollution of the npm registry and inflate developer reputation scores fraudulently, posing a risk to developers and users relying on the integrity of npm packages.

How To Fix

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

npm uninstall teagood-yakuza5

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-yakuza5 package and any other packages associated with the tea.xyz token reward campaign. Additionally, you can monitor your project's dependencies using tools like Vulert, which can alert you to any vulnerabilities in real-time without requiring code access or installation.

Conclusion

The teagood-yakuza5 package poses a significant threat due to its malicious behavior aimed at manipulating npm registry metadata. It is crucial for developers to remain vigilant and take necessary actions to protect their projects from such vulnerabilities.

See every vulnerability recorded for teagood-yakuza5 →

Share this vulnerability

FAQ

teagood-yakuza5 is an npm package involved in a malicious campaign that affects the npm registry by publishing derivative packages.

The vulnerability can lead to the pollution of the npm registry and compromise the integrity of your project's dependencies, potentially introducing malicious code.

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

You can use Vulert to monitor your project's package-lock.json file for vulnerabilities in real-time without requiring code access or installation.

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

How To Fix

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

npm uninstall teagood-yakuza5

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