Malicious Code Injection in teagood-yakuza71: npm Package Vulnerability
Summary
MAL-2025-168032: Malicious code in teagood-yakuza71 (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-yakuza71 is an npm package that is part of the tea.xyz token reward campaign. This package is designed to facilitate token rewards for developers by generating and publishing derivative packages. However, it has been identified as containing malicious code that compromises its integrity and the npm ecosystem.
Vulnerability Detail
The vulnerability in teagood-yakuza71 stems from its malicious code that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior is intended to inflate developer reputation scores and pollute the npm registry with numerous derivative packages. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which has been associated with various malicious npm packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall teagood-yakuza71If 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 remove the affected package from your project by executing: npm uninstall teagood-yakuza71. This will prevent any malicious code from executing until a secure version is available.
Conclusion
The teagood-yakuza71 npm package contains a serious vulnerability due to malicious code that alters project files and publishes unauthorized packages. It is crucial for developers to take immediate action by updating or removing the package to safeguard their projects.
See every vulnerability recorded for teagood-yakuza71 →
FAQ
The vulnerability can lead to unauthorized modifications of your project's package.json file, potentially allowing for the installation of malicious dependencies.
You can use Vulert to monitor and alert for open-source vulnerabilities in your software. Visit the Vulert playground at Vulert Scanner to check your application without any signup.
If an immediate update is not possible, consider removing the package as a temporary measure to mitigate risks associated with the vulnerability.
While specific exploits have not been detailed, the malicious behavior of the package suggests potential for significant disruption and compromise of project integrity.
Regularly audit your dependencies, use tools like Vulert for real-time monitoring, and stay informed about vulnerabilities in the packages you use.
