Malicious Code Injection in tealove-coki39: A Threat to npm Ecosystem
Summary
MAL-2025-168196: Malicious code in tealove-coki39 (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-coki39 is part of a broader campaign associated with the tea.xyz token reward initiative. This package, like others in the campaign, is designed to manipulate the npm registry by generating and publishing derivative packages with randomized names. Its primary function is to inflate developer reputation scores for token rewards, making it a significant concern for developers relying on npm for package management.
Vulnerability Detail
The vulnerability in tealove-coki39 originates from its malicious code, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior leads to the continuous republishing of variants, polluting the npm registry and potentially compromising the integrity of applications that depend on these packages. The malicious payload can affect the reputation of developers and the overall trust in the npm ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall tealove-coki39If 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-coki39 package and replace it with a trusted alternative. Always review the packages you include in your project for any signs of malicious behavior.
Conclusion
The tealove-coki39 package poses a significant threat to the npm ecosystem due to its malicious code that modifies package metadata and repopulates the registry with harmful variants. It is crucial for developers to remain vigilant, regularly audit their dependencies, and utilize tools like Vulert to monitor for vulnerabilities.
See every vulnerability recorded for tealove-coki39 →
FAQ
Tealove-coki39 is an npm package associated with a token reward campaign that generates and publishes malicious derivative packages.
The vulnerability can lead to the pollution of the npm registry, potentially compromising the integrity of your application and affecting its performance.
You should uninstall the package immediately using 'npm uninstall tealove-coki39' and review your project for any other potentially harmful packages.
You can use tools like Vulert, which monitors your package-lock.json file to alert you in real-time for open-source vulnerabilities without requiring code access.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.
