Malicious Code Injection in tealove-poke15: A Threat to npm Users

tealove-poke15 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-168641: Malicious code in tealove-poke15 (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

tealove-poke15 is an npm package that is part of the tea.xyz token reward campaign. This package, like many others in the campaign, is designed to inflate developer reputation scores by automatically generating and publishing derivative packages with randomized names. The malicious nature of this package lies in its ability to modify critical files and republish variants, which can lead to significant pollution of the npm registry.

Vulnerability Detail

The vulnerability in tealove-poke15 originates from its design to include autopublish scripts that alter the package.json file. This modification removes private flags, changes version numbers, and generates random package names, thereby allowing the package to continuously republish itself and its variants. This behavior not only compromises the integrity of the npm registry but also poses risks to developers who may unknowingly install these malicious packages, leading to potential security breaches in their applications.

How To Fix

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

npm uninstall tealove-poke15

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-poke15 package from your project by executing the following command: npm uninstall tealove-poke15. This will prevent any malicious code from executing while you assess the situation and look for a secure alternative.

Conclusion

The tealove-poke15 package poses a significant threat due to its malicious code that alters package files and repopulates the npm registry with potentially harmful variants. It is crucial for developers to stay vigilant, update their packages, and utilize monitoring tools like Vulert to safeguard their projects.

See every vulnerability recorded for tealove-poke15 →

Share this vulnerability

FAQ

tealove-poke15 is an npm package associated with the tea.xyz token reward campaign, designed to inflate developer reputation scores.

The vulnerability allows the package to modify your package.json file and republish itself, which can lead to security risks and pollution of the npm registry.

You should uninstall the package immediately and check for any updates or patches that may address the vulnerability.

You can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities in your software using just package-lock.json. You can check your application for vulnerabilities using the Vulert playground at Vulert Scanner.

Regularly updating your packages, using tools like Vulert for monitoring, and conducting security audits can help prevent vulnerabilities.

How To Fix

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

npm uninstall tealove-poke15

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