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

teagood-yakuza50 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-168009: Malicious code in teagood-yakuza50 (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-yakuza50 is an npm package that is part of the tea.xyz token reward campaign. This package is designed to facilitate token rewards by generating and publishing derivative packages. However, it has been identified as containing malicious code that can compromise the integrity of the npm registry and the applications that depend on it.

Vulnerability Detail

The vulnerability in teagood-yakuza50 originates from its design to automatically generate and publish derivative packages with randomized names. This malicious behavior includes modifying the package.json file to remove private flags, changing version numbers, and continuously republishing variants to pollute the npm registry. The ramifications include potential security risks for developers who unknowingly use these compromised packages, leading to reputation inflation and the spread of malicious code within the ecosystem.

How To Fix

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

npm uninstall teagood-yakuza50

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-yakuza50 package and any other packages associated with the tea.xyz token reward campaign. Additionally, consider using a tool like Vulert to monitor your package-lock.json file for vulnerabilities. You can access the Vulert playground at https://vulert.com/scanner to check if your application is affected by this vulnerability without any signup.

Conclusion

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

See every vulnerability recorded for teagood-yakuza50 →

Share this vulnerability

FAQ

teagood-yakuza50 is an npm package associated with the tea.xyz token reward campaign, designed to generate and publish derivative packages.

The vulnerability can lead to the introduction of malicious code into your application, compromising its security and integrity.

You should uninstall the package immediately using 'npm uninstall teagood-yakuza50' and monitor your project for any other affected packages.

Yes, regularly audit your dependencies using tools like Vulert and stay updated on security advisories related to the packages you use.

Yes, you can use the Vulert playground at Vulert Scanner to check your application for vulnerabilities by simply uploading your package-lock.json file.

How To Fix

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

npm uninstall teagood-yakuza50

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