Malicious Code Injection in teagood-yakuza90: A Threat to npm Users

teagood-yakuza90 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-168053: Malicious code in teagood-yakuza90 (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-yakuza90 is an npm package that is part of the tea.xyz token reward campaign. This package is designed to interact with the npm ecosystem, potentially providing functionalities related to token rewards. However, it has been identified as a malicious package that employs scripts to manipulate its own metadata and publish derivative versions, thereby inflating developer reputation scores for token rewards.

Vulnerability Detail

The vulnerability in teagood-yakuza90 stems from its inclusion in a malicious campaign that uses autopublish scripts to generate and publish numerous derivative packages with randomized names. This behavior not only pollutes the npm registry but also modifies the package.json file to remove private flags and alters version numbers. The ramifications include compromised package integrity, potential security risks for users who install these packages, and a degraded npm ecosystem due to the proliferation of spammy packages.

How To Fix

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

npm uninstall teagood-yakuza90

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 workaround, you can avoid using the teagood-yakuza90 package and monitor your project for any dependencies that may inadvertently include it. Regularly audit your npm packages using tools like npm audit to identify and address vulnerabilities.

Conclusion

The teagood-yakuza90 package poses a significant risk due to its malicious behavior of modifying package metadata and flooding the npm registry with spammy packages. Users are advised to uninstall the package and monitor their dependencies for vulnerabilities. Utilizing tools like Vulert can help maintain the security of your applications.

See every vulnerability recorded for teagood-yakuza90 →

Share this vulnerability

FAQ

teagood-yakuza90 is an npm package associated with the tea.xyz token reward campaign, which has been identified as malicious.

The vulnerability can lead to the installation of malicious code that modifies your package.json file and publishes spammy packages, compromising your project's integrity.

You should uninstall the package immediately using npm uninstall teagood-yakuza90 and audit your project for any other vulnerabilities.

You can use tools like npm audit to check for vulnerabilities in your dependencies and consider using Vulert to monitor your package-lock.json for real-time alerts.

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

How To Fix

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

npm uninstall teagood-yakuza90

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