Malicious Code Injection in tealove-coki33 Package
Summary
MAL-2025-168190: Malicious code in tealove-coki33 (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
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
Background
The tealove-coki33 package is part of the tea.xyz token reward campaign that has infiltrated the npm ecosystem. This package is designed to facilitate the generation and publication of derivative packages, often with randomized names, to inflate developer reputation scores for token rewards. It is primarily used by developers looking to participate in the tea protocol ecosystem, but its malicious nature poses significant risks to users and the npm registry.
Vulnerability Detail
The vulnerability in the tealove-coki33 package stems from its inclusion in a series of malicious packages that contain scripts designed to automatically publish derivative packages. These scripts modify the package.json file to remove private flags, alter version numbers, and generate random package names, leading to pollution of the npm registry. The malicious behavior can compromise the integrity of the npm ecosystem and potentially expose users to security risks.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall tealove-coki33If 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 measure, you can avoid using the tealove-coki33 package and any other packages associated with the tea.xyz token reward campaign. Regularly audit your dependencies to ensure no malicious packages are included in your project.
Conclusion
The tealove-coki33 package poses a significant risk due to its malicious code designed to manipulate the npm registry. It is crucial for developers to be vigilant about the packages they include in their projects and to take immediate action to remove any malicious packages. Utilizing tools like Vulert can help in monitoring and preventing future vulnerabilities.
See every vulnerability recorded for tealove-coki33 →
FAQ
Tealove-coki33 is an npm package that is part of a malicious campaign aimed at inflating developer reputation scores through the automatic generation of derivative packages.
The vulnerability can lead to the pollution of the npm registry, potentially exposing your project to security risks and compromising the integrity of your dependencies.
You should uninstall the tealove-coki33 package immediately using the command: npm uninstall tealove-coki33.
Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in your software using just the package-lock.json file. You can check your application for vulnerabilities using the Vulert playground without any signup.
Regularly audit your dependencies, use tools like Vulert for monitoring, and stay informed about known vulnerabilities in the packages you use.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
