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

teagood-yakuza28 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-167985: Malicious code in teagood-yakuza28 (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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

teagood-yakuza28 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 generating and publishing numerous derivative packages with randomized names. Its primary function is to inflate developer reputation scores for rewards associated with the tea protocol, but this comes at the cost of security and integrity within the npm ecosystem.

Vulnerability Detail

The vulnerability in teagood-yakuza28 stems from its 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, thereby polluting the npm registry. The origin of this issue is linked to a campaign that exploits npm's publishing capabilities, potentially leading to reputation damage for developers and security risks for users who inadvertently install these malicious packages.

How To Fix

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

npm uninstall teagood-yakuza28

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 prevent the installation of the vulnerable package by using the npm shrinkwrap feature or by manually removing it from your package.json file. Additionally, you can monitor your dependencies using tools like Vulert, which can alert you to vulnerabilities in real-time without requiring code access.

Conclusion

The teagood-yakuza28 package poses a significant risk due to its malicious behavior aimed at manipulating the npm registry. Users are advised to update or remove the package to safeguard their projects. Utilizing tools like Vulert can further enhance security by providing real-time vulnerability alerts.

See every vulnerability recorded for teagood-yakuza28 →

Share this vulnerability

FAQ

teagood-yakuza28 is an npm package involved in a token reward campaign that manipulates the npm registry.

The vulnerability can lead to the installation of malicious packages that may compromise your project's security and integrity.

You should update the package to a patched version if available or remove it from your project to avoid potential risks.

Yes, you can use Vulert to monitor your package-lock.json file for vulnerabilities in real-time without needing to install any additional software.

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-yakuza28

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