Malicious Code Injection in tealove-coki23: npm Package Vulnerability

tealove-coki23 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-168179: Malicious code in tealove-coki23 (npm). Affected versions are not published. No fix is published. How to fix ↓

Free scan

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.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The package tealove-coki23 is part of the tea.xyz token reward campaign, which has been associated with numerous malicious packages flooding the npm ecosystem. This package is designed to manipulate developer reputation scores by automatically generating and publishing derivative packages with randomized names. Its primary function is to facilitate the distribution of these derivative packages, which can lead to significant pollution of the npm registry.

Vulnerability Detail

The vulnerability in tealove-coki23 originates from its inclusion in a campaign that utilizes autopublish scripts to create and publish numerous variants of itself. These scripts modify the package.json file to remove private flags, alter version numbers, and generate random package names, which can lead to an inflated reputation score for the developers involved. The continuous republishing of these variants can clutter the npm registry, making it difficult for legitimate packages to be discovered and used. This poses a risk not only to developers but also to end-users who may inadvertently install compromised packages.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall tealove-coki23

If 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 tealove-coki23 and any other packages associated with the tea.xyz token reward campaign. Regularly audit your project's dependencies using tools like npm audit to identify and remove any potentially malicious packages.

Conclusion

The tealove-coki23 package poses a significant risk due to its malicious code designed to manipulate npm's package registry. It is crucial for developers to be vigilant about the packages they use and to regularly audit their dependencies to maintain the security and integrity of their projects.

See every vulnerability recorded for tealove-coki23 →

Share this vulnerability

FAQ

Tealove-coki23 is an npm package that is part of a malicious campaign aimed at inflating developer reputation scores through the automatic generation and publication of derivative packages.

The vulnerability can lead to the pollution of the npm registry, making it difficult to find legitimate packages and potentially exposing your project to security risks from malicious code.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. By utilizing the Vulert playground, you can check if your application is affected by this vulnerability without any signup.

If you have installed tealove-coki23, you should uninstall it immediately using the command npm uninstall tealove-coki23 and audit your dependencies for any other malicious packages.

Yes, tools like npm audit and Vulert can help you identify and manage vulnerabilities in your npm packages effectively.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall tealove-coki23

If 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 →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback