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

teagood-yakuza3 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-167987: Malicious code in teagood-yakuza3 (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 Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

teagood-yakuza3 is an npm package that is part of the tea.xyz token reward campaign. This package is designed to interact with the npm registry and is often used by developers to manage dependencies in their JavaScript applications. However, it has been identified as containing malicious code that can compromise the integrity of the npm ecosystem.

Vulnerability Detail

The vulnerability in teagood-yakuza3 originates from its inclusion in a series of malicious packages aimed at inflating developer reputation scores for token rewards. The malicious payload modifies the package.json file by removing private flags, altering version numbers, and generating random package names. This behavior leads to the continuous republishing of variants, polluting the npm registry and potentially affecting other packages and applications that depend on it.

How To Fix

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

npm uninstall teagood-yakuza3

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 remove the teagood-yakuza3 package from your project by executing 'npm uninstall teagood-yakuza3'. This will prevent any malicious code from executing while you assess your dependencies.

Conclusion

The teagood-yakuza3 package poses a significant threat to the npm ecosystem due to its malicious code. It is crucial for developers to be vigilant, update their packages regularly, and utilize tools like Vulert to monitor for vulnerabilities. Taking proactive measures can help safeguard applications from potential threats.

See every vulnerability recorded for teagood-yakuza3 →

Share this vulnerability

FAQ

teagood-yakuza3 is an npm package that is part of a token reward campaign, which has been identified to contain malicious code.

The malicious code modifies your package.json file and can lead to the pollution of the npm registry, affecting other packages and applications.

You should uninstall the package immediately and check for any updates or patches that may be available.

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

Regularly update your dependencies, use tools like Vulert for monitoring, and audit your packages to ensure they are safe.

How To Fix

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

npm uninstall teagood-yakuza3

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