Malicious Code Injection in teagood-cuekin86: A Threat to npm Ecosystem
Summary
MAL-2025-166855: Malicious code in teagood-cuekin86 (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-cuekin86 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 scripts that compromise its integrity and the npm registry.
Vulnerability Detail
The vulnerability in teagood-cuekin86 originates from its inclusion in a campaign that floods the npm registry with malicious packages. It contains scripts that modify the package.json file to remove private flags, alter version numbers, and generate random package names. This behavior leads to the continuous republishing of variants, polluting the npm registry and potentially harming developers who rely on legitimate packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall teagood-cuekin86If 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 package from your project by executing the following command: 'npm uninstall teagood-cuekin86'. This will prevent any malicious scripts from executing in your environment.
Conclusion
The teagood-cuekin86 package poses a significant threat due to its malicious code that alters package configurations and floods the npm registry with harmful variants. Developers are urged to take immediate action by updating or removing the package to safeguard their projects.
See every vulnerability recorded for teagood-cuekin86 →
FAQ
The primary risk is the injection of malicious code that modifies package.json, leading to the creation of numerous harmful packages in the npm registry.
You can use Vulert to monitor and alert for open-source vulnerabilities in your software. Visit Vulert Scanner to check if your application is affected without any signup.
If you cannot update the package, it is advisable to remove it from your project to avoid potential security risks.
Yes, the malicious scripts included in the package can lead to the automatic generation of harmful packages, which can affect other developers and the integrity of the npm registry.
Vulert uses package-lock.json to monitor and alert in real-time for open-source vulnerabilities, helping developers maintain secure applications.
