Malicious Code Injection in teagood-yakuza4 Package - npm Vulnerability
Summary
MAL-2025-167997: Malicious code in teagood-yakuza4 (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
The teagood-yakuza4 package is part of a series of npm packages associated with the tea.xyz token reward campaign. These packages are designed to automate the generation and publication of derivative packages, often with randomized names, to inflate developer reputation scores for token rewards. This behavior poses significant risks to the integrity of the npm registry and the security of applications relying on these packages.
Vulnerability Detail
The vulnerability in the teagood-yakuza4 package stems from malicious code that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This code is designed to continuously republish variants of the package, polluting the npm registry and potentially leading to security risks for developers who unknowingly install these compromised packages. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which has flooded the npm ecosystem with such malicious packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall teagood-yakuza4If 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 workaround, consider using a package-lock.json file to lock your dependencies to specific versions, preventing the installation of compromised packages. Additionally, you can monitor your project for vulnerabilities using tools like Vulert. You can check if your application is affected by this vulnerability without any signup by visiting the Vulert playground at https://vulert.com/scanner.
Conclusion
The teagood-yakuza4 package presents a significant security risk due to its malicious code designed to manipulate package metadata and republish variants. It is crucial for developers to remove this package from their projects and utilize tools like Vulert to monitor for vulnerabilities in their dependencies.
See every vulnerability recorded for teagood-yakuza4 →
FAQ
teagood-yakuza4 is an npm package that is part of a malicious campaign aimed at inflating developer reputation scores through automated package publishing.
The malicious code modifies your package.json file and can lead to the installation of compromised packages, potentially exposing your application to security risks.
You should immediately remove the teagood-yakuza4 package from your project and monitor for any updates or patches that may address the vulnerability.
Regularly audit your dependencies, use tools like Vulert to monitor for vulnerabilities, and lock your package versions using package-lock.json.
Yes, you can use the Vulert playground at Vulert Scanner to check for vulnerabilities in your application without needing to sign up.
