Malicious Code Injection in tealove-coki15 Package

tealove-coki15 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-168170: Malicious code in tealove-coki15 (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 Devnack Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The tealove-coki15 package is part of the tea.xyz token reward campaign, which has been known to flood the npm ecosystem with various packages. These packages are designed to manipulate developer reputation scores by automatically generating and publishing derivative packages with randomized names. The functionality of tealove-coki15 is compromised due to its malicious intent, which aims to exploit the npm registry.

Vulnerability Detail

The vulnerability in the tealove-coki15 package originates from its design to include autopublish scripts that modify the package.json file. This modification removes private flags, alters version numbers, and generates random package names, leading to the continuous republishing of variants. This behavior not only pollutes the npm registry but also poses a risk to developers who may unknowingly use these compromised packages, potentially leading to security breaches and loss 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-coki15

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 monitor your project's dependencies using tools like Vulert. By utilizing Vulert's playground at https://vulert.com/scanner, you can check if your application is affected by this vulnerability without requiring any installation or signup.

Conclusion

The tealove-coki15 package poses a significant risk due to its malicious code designed to manipulate the npm registry. It is crucial for developers to be vigilant about their dependencies and utilize tools like Vulert to monitor for vulnerabilities. Removing compromised packages and staying informed can help maintain the integrity of your projects.

See every vulnerability recorded for tealove-coki15 →

Share this vulnerability

FAQ

Tealove-coki15 is an npm package that is part of a token reward campaign, known for flooding the npm registry with malicious packages.

The vulnerability can lead to the modification of your package.json file, potentially exposing your project to security risks and affecting your reputation as a developer.

You should immediately uninstall the package using the command 'npm uninstall tealove-coki15' and review your project's dependencies for any other malicious packages.

Yes, regularly monitor your dependencies using tools like Vulert to receive real-time alerts for open-source vulnerabilities.

Yes, you can use the Vulert playground at Vulert Scanner to check for vulnerabilities in your application without any signup.

How To Fix

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

npm uninstall tealove-coki15

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