Malicious Code Injection in tealove-coki35: npm Package Vulnerability
Summary
MAL-2025-168192: Malicious code in tealove-coki35 (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-coki35 is part of the tea.xyz token reward campaign, which has been known to flood the npm registry with malicious packages. These packages are designed to inflate developer reputation scores through automated scripts that generate and publish numerous derivative packages with randomized names. This behavior not only clutters the npm registry but also poses a significant risk to developers who may inadvertently use these compromised packages.
Vulnerability Detail
The vulnerability in tealove-coki35 stems from its inclusion in a campaign that utilizes autopublish scripts to modify package.json files. This malicious payload removes private flags, alters version numbers, and generates random package names, leading to the continuous republishing of variants that pollute the npm registry. The ramifications include potential exposure of sensitive data, compromised application integrity, and a general degradation of 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-coki35If 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, you can avoid using the tealove-coki35 package altogether and consider alternative packages that provide similar functionality without the associated risks. Additionally, regularly audit your project's dependencies using tools like npm audit to identify and mitigate vulnerabilities.
Conclusion
The tealove-coki35 package presents a significant security risk due to its malicious code that modifies package configurations and repopulates the npm registry with compromised packages. It is crucial for developers to remove this package and stay vigilant by monitoring their dependencies for vulnerabilities.
See every vulnerability recorded for tealove-coki35 →
FAQ
Tealove-coki35 is an npm package that is part of a malicious campaign aimed at inflating developer reputation scores through automated publishing of derivative packages.
The vulnerability can lead to the exposure of sensitive data and compromise the integrity of your application by introducing malicious code.
You should remove the package from your project immediately and monitor for any updates or patches that may address the vulnerability.
You can use tools like npm audit to regularly check your project's dependencies for known vulnerabilities.
Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time using just your package-lock.json. You can check your application at Vulert Playground without any signup.
