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

teagood-yakuza84 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-168046: Malicious code in teagood-yakuza84 (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 Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

Background

teagood-yakuza84 is an npm package that is part of a broader campaign involving the tea.xyz token reward system. This package, like others in the campaign, is designed to manipulate the npm registry by automatically generating and publishing derivative packages with randomized names. Its primary function is to inflate developer reputation scores for rewards associated with the tea protocol, but it has been compromised to include malicious code.

Vulnerability Detail

The vulnerability stems from the package's malicious payload, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior leads to the continuous republishing of variants, polluting the npm registry and potentially compromising other packages. The origin of this issue is linked to the tea.xyz token reward campaign, which has flooded npm with similar malicious packages.

How To Fix

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

npm uninstall teagood-yakuza84

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 and monitor your project for any dependencies that may indirectly rely on it. Additionally, consider using tools like Vulert to monitor your package-lock.json for vulnerabilities.

Conclusion

The teagood-yakuza84 package poses a significant risk due to its malicious code that alters package metadata and pollutes the npm registry. It is crucial for developers to take immediate action by removing the package and monitoring their projects for vulnerabilities. Utilizing tools like Vulert can aid in maintaining the security of your applications.

See every vulnerability recorded for teagood-yakuza84 →

Share this vulnerability

FAQ

teagood-yakuza84 is an npm package involved in a token reward campaign that has been compromised to include malicious code.

The malicious code modifies your package.json, removes private flags, and generates random package names, which can lead to pollution of the npm registry and potential security risks.

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

Regularly update your dependencies, use tools like Vulert to monitor for vulnerabilities, and review your package-lock.json for any suspicious packages.

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

Sponsored Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

How To Fix

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

npm uninstall teagood-yakuza84

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