Malicious Code Injection in tealove-coki2: A Threat to npm Users
Summary
MAL-2025-168175: Malicious code in tealove-coki2 (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 tealove-coki2 is part of a broader campaign associated with the tea.xyz token reward system. It is designed to manipulate the npm ecosystem by generating and publishing numerous derivative packages with randomized names. This behavior is intended to inflate developer reputation scores in exchange for tea protocol token rewards. The package's functionality is compromised due to its malicious intent, posing a significant risk to users and the integrity of the npm registry.
Vulnerability Detail
The vulnerability in tealove-coki2 originates from its inclusion in the tea.xyz token reward campaign, which floods the npm registry with malicious packages. These packages contain scripts that modify the package.json file to remove private flags, alter version numbers, and create random package names. This leads to the continuous republishing of these variants, polluting the npm registry and potentially compromising other projects that depend on legitimate packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall tealove-coki2If 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, users can manually check their package-lock.json file for any instances of tealove-coki2 and remove it. Additionally, consider using tools like Vulert to monitor your project for vulnerabilities. You can check if your application is affected by this vulnerability using the Vulert playground at https://vulert.com/scanner without any signup.
Conclusion
The tealove-coki2 package poses a significant threat to the npm ecosystem due to its malicious behavior aimed at inflating developer reputation scores. Users are advised to remove this package and monitor their projects for vulnerabilities to maintain the integrity of their applications.
See every vulnerability recorded for tealove-coki2 →
FAQ
Tealove-coki2 is an npm package that is part of a malicious campaign aimed at inflating developer reputation scores through the creation of numerous derivative packages.
The vulnerability can lead to the pollution of the npm registry, potentially causing conflicts or issues in your project if it relies on affected packages.
You should remove the tealove-coki2 package from your project immediately and monitor your dependencies for any other malicious packages.
Currently, there is no patched version of tealove-coki2 available. It is advisable to avoid using this package altogether.
You can use tools like Vulert, which monitors your package-lock.json file for open-source vulnerabilities in real-time. You can also check your application against known vulnerabilities using the Vulert playground.
