Malicious Code Injection in teagood-yakuna67: A Threat to npm Ecosystem
Summary
MAL-2025-167928: Malicious code in teagood-yakuna67 (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 package 'teagood-yakuna67' is part of a series of npm packages associated with the tea.xyz token reward campaign. These packages are designed to inflate developer reputation scores by automatically generating and publishing derivative packages with randomized names. The malicious nature of this package lies in its ability to modify essential files and republish variants, thereby polluting the npm registry.
Vulnerability Detail
The vulnerability in 'teagood-yakuna67' originates from its design to include autopublish scripts that alter the package.json file by removing private flags and changing version numbers. This allows the package to generate random names, primarily themed around Indonesian culture, and continuously republish these variants. The ramifications include potential security risks for developers who unknowingly use these packages, as they can lead to reputation damage and the spread of malicious code within the npm ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall teagood-yakuna67If 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, avoid using the 'teagood-yakuna67' package and monitor your package-lock.json for any dependencies that may include it. You can also use the following command to check for vulnerabilities in your project: 'npm audit'.
Conclusion
The 'teagood-yakuna67' package poses a significant threat to the npm ecosystem due to its malicious code that alters package files and repopulates the registry with harmful variants. It is essential for developers to remain vigilant, regularly audit their dependencies, and utilize tools like Vulert to safeguard their projects.
See every vulnerability recorded for teagood-yakuna67 →
FAQ
The primary risk is the injection of malicious code that can alter your project's package.json file, leading to potential security vulnerabilities and reputation damage.
You can use the Vulert service, which monitors your package-lock.json for vulnerabilities. Visit Vulert Scanner to check if your application is affected without requiring any signup.
Immediately uninstall the package using 'npm uninstall teagood-yakuna67' and review your project for any other potentially affected packages.
Yes, tools like Vulert can help monitor and alert you in real-time for open-source vulnerabilities in your software.
Remove any identified malicious packages and ensure to regularly audit your dependencies using 'npm audit' to maintain a secure project.
