Malicious Code Injection in tealove-coki42: A Threat to npm Ecosystem
Summary
MAL-2025-168200: Malicious code in tealove-coki42 (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-coki42 is part of a broader campaign associated with the tea.xyz token reward initiative. It is designed to manipulate the npm registry by automatically generating and publishing derivative packages. This behavior aims to inflate developer reputation scores in exchange for tea protocol token rewards. The package's functionality is compromised due to its malicious intent, making it a significant risk to developers and users relying on npm packages.
Vulnerability Detail
The vulnerability in tealove-coki42 originates from its inclusion in a malicious campaign that floods the npm registry with derivative packages. The malicious payload modifies the package.json file by removing private flags, altering version numbers, and generating random package names, which can lead to pollution of the npm registry. This behavior can compromise the integrity of the npm ecosystem, making it difficult for developers to trust the packages they use.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall tealove-coki42If 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 avoid using the tealove-coki42 package altogether. If you need similar functionality, consider using alternative packages that are well-reviewed and have a good reputation in the community.
Conclusion
The tealove-coki42 package poses a significant threat to the npm ecosystem due to its malicious code that modifies package metadata and floods the registry with untrustworthy packages. It is essential to remove this package from your projects and monitor for vulnerabilities using tools like Vulert to maintain the integrity of your software.
See every vulnerability recorded for tealove-coki42 →
FAQ
Tealove-coki42 is an npm package that is part of a malicious campaign aimed at manipulating the npm registry.
The vulnerability can lead to the pollution of the npm registry, making it difficult to trust other packages and potentially compromising your project's security.
You should uninstall the package immediately using 'npm uninstall tealove-coki42' and check for any alternative packages.
You can use tools like Vulert, which monitors your package-lock.json file for vulnerabilities in real-time without requiring code access or installation.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without signing up.
