Malicious Code Injection in tealove-poke48: A Threat to npm Ecosystem

tealove-poke48 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-168675: Malicious code in tealove-poke48 (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 Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

Background

tealove-poke48 is an npm package that is part of the tea.xyz token reward campaign. This package is designed to interact with the npm ecosystem, potentially providing functionalities related to token rewards. However, it has been identified as malicious, containing scripts that manipulate package metadata and flood the npm registry with derivative packages, thereby compromising the integrity of the ecosystem.

Vulnerability Detail

The vulnerability in tealove-poke48 originates from its malicious code that modifies the package.json file to remove private flags and change version numbers. It generates random package names and continuously republishes variants, which can lead to pollution of the npm registry and inflate developer reputation scores fraudulently. This poses a significant risk to developers relying on the integrity of the npm ecosystem, as it can lead to confusion, dependency issues, and potential security risks.

How To Fix

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

npm uninstall tealove-poke48

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

Currently, there are no specific workarounds to mitigate the effects of this vulnerability other than removing the affected package. It is advisable to monitor your dependencies regularly and avoid using packages that are part of the tea.xyz token reward campaign.

Conclusion

The tealove-poke48 package poses a significant threat to the npm ecosystem due to its malicious code that manipulates package metadata and floods the registry with derivative packages. It is crucial for developers to remove this package from their projects and monitor their dependencies to maintain the integrity of their applications.

See every vulnerability recorded for tealove-poke48 →

Share this vulnerability

FAQ

tealove-poke48 is an npm package associated with the tea.xyz token reward campaign, which has been identified as containing malicious code.

The vulnerability can lead to the pollution of the npm registry, confusion in package management, and potential security risks due to the introduction of malicious code.

You should uninstall the package immediately using 'npm uninstall tealove-poke48' and check your package-lock.json for any references to it.

Yes, you can use Vulert to monitor and alert in real-time for open-source vulnerabilities in your software. It requires only the package-lock.json file for analysis.

You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.

Sponsored Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

How To Fix

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

npm uninstall tealove-poke48

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