Malicious Code Injection in teagood-yakuza81: A Threat to npm Packages
Summary
MAL-2025-168043: Malicious code in teagood-yakuza81 (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-yakuza81 is an npm package that is part of the tea.xyz token reward campaign. This package is designed to interact with the npm registry, allowing developers to publish and manage packages. However, it has been identified as containing malicious code that can compromise the integrity of the npm ecosystem.
Vulnerability Detail
The vulnerability in teagood-yakuza81 originates from its inclusion in a campaign that floods the npm registry with derivative packages. The malicious code modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior can lead to the pollution of the npm registry, potentially affecting developers' reputations and the security of their applications.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall teagood-yakuza81If 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 the command: 'npm uninstall teagood-yakuza81'. This will prevent any malicious code from executing while you seek a more permanent solution.
Conclusion
The teagood-yakuza81 package poses a significant risk due to its malicious code that manipulates the npm registry. Developers should take immediate action to remove or update the package to safeguard their applications and maintain the integrity of the npm ecosystem.
See every vulnerability recorded for teagood-yakuza81 →
FAQ
The primary issue is that it contains malicious code designed to manipulate the npm registry and inflate developer reputation scores.
You can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.
Using this package can lead to the pollution of the npm registry, affecting your project's integrity and potentially damaging your reputation as a developer.
Regularly auditing your dependencies and using tools like Vulert can help monitor and alert you to open-source vulnerabilities in your software.
If you cannot update or remove the package, consider isolating it in a separate environment and monitoring its behavior closely until a solution is found.
