Malicious Code Vulnerability in tealove-coki11 Package

tealove-coki11 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-168166: Malicious code in tealove-coki11 (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-coki11 package is part of the tea.xyz token reward campaign, which has been known to flood the npm registry with various packages. These packages are designed to inflate developer reputation scores by automatically generating and publishing derivative packages with randomized names. The functionality of tealove-coki11 is compromised due to its association with malicious scripts that manipulate package metadata.

Vulnerability Detail

The vulnerability in the tealove-coki11 package originates from its inclusion in a malicious campaign that modifies the package.json file to remove private flags and alters version numbers. It generates random package names and continuously republishes variants, leading to pollution of the npm registry. This can result in developers inadvertently using compromised packages, exposing their applications to potential security risks.

How To Fix

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

npm uninstall tealove-coki11

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 temporary workaround, you can remove the tealove-coki11 package from your project by executing: npm uninstall tealove-coki11. This will prevent any potential exploitation until a secure version is available.

Conclusion

The tealove-coki11 package contains a significant vulnerability due to its malicious code that modifies package metadata and repopulates the npm registry with compromised packages. It is crucial for developers to take immediate action to update or remove this package to safeguard their applications.

See every vulnerability recorded for tealove-coki11 →

Share this vulnerability

FAQ

Tealove-coki11 is an npm package that is part of a token reward campaign, which has been associated with malicious activities aimed at inflating developer reputation scores.

The vulnerability can lead to the inclusion of malicious code in your application, potentially compromising its security and integrity.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without requiring any signup.

If an immediate update is not possible, consider removing the package from your project as a temporary measure to mitigate risks.

Detailed information about this vulnerability can be found in the npm registry and security advisories related to the tealove-coki11 package.

How To Fix

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

npm uninstall tealove-coki11

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