Malicious Code Injection in teagood-yakuza68: npm Package Vulnerability
Summary
MAL-2025-168028: Malicious code in teagood-yakuza68 (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-yakuza68 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. Its primary function is to inflate developer reputation scores for token rewards, but it has been compromised to include malicious scripts that manipulate package metadata.
Vulnerability Detail
The vulnerability in teagood-yakuza68 stems from its inclusion in a campaign that floods the npm registry with malicious packages. The malicious code modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This leads to the continuous republishing of these variants, polluting the npm registry and potentially compromising the integrity of other packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall teagood-yakuza68
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 avoid using the teagood-yakuza68 package altogether. If it is already in use, consider removing it from your package.json and running npm install to clean up your dependencies.
Conclusion
The teagood-yakuza68 package has been identified as containing malicious code that compromises the integrity of the npm registry. It is crucial for developers to remove this package from their projects and monitor for any updates or patches. Utilizing tools like Vulert can help in identifying vulnerabilities in your dependencies.
See every vulnerability recorded for teagood-yakuza68 →
FAQ
The vulnerability can lead to the pollution of the npm registry, affecting the integrity of other packages and potentially compromising applications that rely on them.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. Visit Vulert Scanner to check if your application is affected without requiring any signup.
If you have installed teagood-yakuza68, it is advisable to remove it immediately and check for any dependencies that may have been affected.
Currently, there is no specific patch for teagood-yakuza68. The best course of action is to remove the package until a secure version is released.
This vulnerability can compromise your project's security by introducing malicious code, which may lead to unauthorized access or data manipulation.