Malicious Code Injection in tealove-coki36: A Threat to npm Ecosystem
Summary
MAL-2025-168193: Malicious code in tealove-coki36 (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-coki36 is part of the tea.xyz token reward campaign, which has been associated with a series of malicious npm packages. These packages are designed to inflate developer reputation scores through the automatic generation and publication of derivative packages with randomized names. The functionality of tealove-coki36 is compromised by malicious scripts that manipulate its metadata and continuously pollute the npm registry.
Vulnerability Detail
The vulnerability in tealove-coki36 originates from its inclusion in a campaign that floods the npm registry with malicious packages. The malicious code modifies the package.json file by removing private flags, altering version numbers, and generating random package names. This not only affects the integrity of the package but also poses a risk of reputation damage to developers and can lead to the spread of further malicious packages across the npm ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall tealove-coki36If 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 prevent the installation of this package by using npm's package-lock.json to monitor dependencies. You can also utilize tools like Vulert to check for vulnerabilities in your project without needing to access the code directly. To check if your application is affected, visit the Vulert playground at https://vulert.com/scanner.
Conclusion
The tealove-coki36 package poses a significant threat to the npm ecosystem due to its malicious code that manipulates package metadata. It is crucial for developers to be vigilant, remove affected packages, and utilize tools like Vulert to monitor for vulnerabilities in their projects.
See every vulnerability recorded for tealove-coki36 →
FAQ
Tealove-coki36 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 modification of your project's package.json file, potentially exposing your project to further malicious activities and damaging your reputation as a developer.
You should uninstall the package immediately using 'npm uninstall tealove-coki36' and monitor your project for any other vulnerabilities.
You can use tools like Vulert, which allows you to monitor and alert for open-source vulnerabilities in real-time using just your package-lock.json file.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.
