Malicious Code Injection in teagood-yakuza34: npm Package Vulnerability
Summary
MAL-2025-167992: Malicious code in teagood-yakuza34 (npm). Affected versions are not published. No fix is published. How to fix ↓
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.
No signup required · Results in about 60 seconds
Background
teagood-yakuza34 is an npm package that appears to be part of a token reward campaign associated with the tea.xyz protocol. This package is designed to facilitate the generation and publication of derivative packages, often with randomized names, to inflate developer reputation scores for token rewards. Its functionality is compromised due to the presence of malicious scripts that manipulate package metadata.
Vulnerability Detail
The vulnerability in teagood-yakuza34 originates from malicious code embedded within the package. This code is designed to automatically modify the package.json file by removing private flags, changing version numbers, and generating random package names. The scripts (auto.js, autopublish.js, etc.) continuously republish these variants, leading to pollution of the npm registry and potential security risks for developers who unknowingly use these packages. The ramifications include compromised package integrity and the potential for malicious exploitation of affected systems.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall teagood-yakuza34If 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-yakuza34 package and look for alternative packages that provide similar functionality without the associated risks. Always verify the integrity and source of packages before installation.
Conclusion
The teagood-yakuza34 npm package contains malicious code that poses significant risks to developers and the integrity of the npm registry. It is crucial to remove this package from your projects and to adopt best practices for package management to safeguard against future vulnerabilities.
See every vulnerability recorded for teagood-yakuza34 →
FAQ
The main issue is the presence of malicious code that modifies package metadata and republish variants, which can compromise the integrity of the npm registry.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. Visit Vulert Scanner to check your application without needing to sign up.
If you have installed teagood-yakuza34, you should uninstall it immediately using the command npm uninstall teagood-yakuza34.
Yes, you should look for reputable packages that offer similar functionality while ensuring they are free from malicious code.
To prevent similar vulnerabilities, regularly audit your dependencies, use trusted sources for packages, and keep your software updated.
