Malicious Code Injection in tealove-coki46: A Threat to npm Packages

tealove-coki46 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-168204: Malicious code in tealove-coki46 (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 Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The package tealove-coki46 is part of a broader campaign associated with the tea.xyz token reward initiative. This npm package is designed to automate the generation and publication of derivative packages, often with randomized names, to artificially inflate developer reputation scores in exchange for tea protocol token rewards. Its functionality is compromised by malicious scripts that manipulate package metadata.

Vulnerability Detail

The vulnerability in tealove-coki46 stems from its inclusion in a malicious campaign that utilizes scripts (auto.js, autopublish.js, etc.) to modify the package.json file. This modification removes private flags, alters version numbers, and generates random package names, leading to pollution of the npm registry. The ramifications include potential security risks for developers who unknowingly install these compromised packages, as they may inadvertently expose their applications to further vulnerabilities.

How To Fix

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

npm uninstall tealove-coki46

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 avoid using tealove-coki46 and any other packages associated with the tea.xyz campaign. Regularly audit your package.json and package-lock.json files to ensure no malicious packages are included.

Conclusion

The tealove-coki46 package poses a significant risk due to its malicious code designed to manipulate npm package metadata. Developers should take immediate action to remove this package and monitor their applications for similar vulnerabilities. Utilizing tools like Vulert can aid in maintaining the security of your software.

See every vulnerability recorded for tealove-coki46 →

Share this vulnerability

FAQ

Tealove-coki46 is an npm package that is part of a malicious campaign aimed at inflating developer reputation scores through automated package publishing.

The vulnerability can lead to the installation of compromised packages, which may introduce security risks and instability in your application.

You should uninstall the package immediately using 'npm uninstall tealove-coki46' and check for any other affected packages.

You can use tools like Vulert, which monitors your package-lock.json file to alert you in real-time about open-source vulnerabilities.

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

How To Fix

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

npm uninstall tealove-coki46

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