Malicious Code Injection in teagood-yakuna87: A Threat to npm Packages
Summary
MAL-2025-167950: Malicious code in teagood-yakuna87 (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-yakuna87 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, which are often used to inflate developer reputation scores for token rewards. However, it has been identified as containing malicious code that compromises its integrity and the security of the npm ecosystem.
Vulnerability Detail
The vulnerability in teagood-yakuna87 originates from its malicious payload that modifies the package.json file. It removes private flags, alters version numbers, and generates random package names, leading to the continuous republishing of variants that pollute the npm registry. This behavior can result in significant security risks, including the potential for dependency confusion and the spread of malicious code across projects that rely on these packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall teagood-yakuna87If 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 teagood-yakuna87 package from your project by executing the following command: npm uninstall teagood-yakuna87. This will prevent any malicious code from executing until a secure version is available.
Conclusion
The teagood-yakuna87 package poses a significant security threat due to its malicious code that alters package metadata and floods the npm registry. It is crucial for developers to take immediate action by updating or removing the package to safeguard their applications. Utilizing tools like Vulert can further enhance security by providing real-time vulnerability alerts.
See every vulnerability recorded for teagood-yakuna87 →
FAQ
The primary risk is the potential for malicious code execution and the pollution of the npm registry, which can lead to dependency confusion and security breaches in dependent projects.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. By utilizing the Vulert playground, you can check if your application is affected without needing to sign up.
If an immediate update is not possible, consider removing the package from your project as a temporary measure to mitigate risks.
Yes, tools like Vulert can help monitor your dependencies for vulnerabilities in real-time, allowing you to stay informed about potential risks.
Using npm packages from unknown sources can be risky. Always verify the source and check for known vulnerabilities before including them in your projects.
