Malicious Code Injection in teagood-yakuza27: npm Package Vulnerability
Summary
MAL-2025-167984: Malicious code in teagood-yakuza27 (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-yakuza27 is an npm package that is part of the tea.xyz token reward campaign. 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. However, it has been identified as containing malicious scripts that compromise its integrity and the npm registry.
Vulnerability Detail
The vulnerability in teagood-yakuza27 originates from its inclusion in a campaign that floods the npm registry with derivative packages. The malicious payload modifies the package.json file by removing private flags, altering version numbers, and generating random package names. This behavior leads to the continuous republishing of variants, polluting the npm registry and potentially harming developers' reputations and the integrity of the ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall teagood-yakuza27If 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 this malicious package by using npm's package-lock.json file to lock your dependencies to safe versions. Additionally, you can run the following command to uninstall the package: npm uninstall teagood-yakuza27.
Conclusion
The teagood-yakuza27 package has been identified as containing malicious code that compromises the npm registry and developer reputations. It is crucial to take immediate action by updating or removing the package to mitigate potential risks.
See every vulnerability recorded for teagood-yakuza27 →
FAQ
The primary issue is that it contains malicious code that modifies package.json files and floods the npm registry with derivative packages.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. Visit the Vulert playground at Vulert Scanner to check if your application is affected without requiring any signup.
The consequences include pollution of the npm registry, potential harm to developer reputations, and the risk of introducing further vulnerabilities into dependent applications.
Yes, you can lock your dependencies using package-lock.json and uninstall the package using the command: npm uninstall teagood-yakuza27.
If you cannot update or remove the package, consider isolating your application from the affected package and monitoring for any unusual behavior.
