Malicious Code Injection in tealove-lady4 Package

tealove-lady4 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-168347: Malicious code in tealove-lady4 (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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The tealove-lady4 package is part of the tea.xyz token reward campaign that has infiltrated the npm ecosystem. It is designed to generate and publish derivative packages with randomized names, which are used to inflate developer reputation scores in exchange for tea protocol token rewards. This package, like others in the campaign, contains scripts that automate the publishing process, leading to potential abuse of the npm registry.

Vulnerability Detail

The vulnerability in the tealove-lady4 package arises from the presence of malicious code that modifies the package.json file. This code removes private flags, alters version numbers, and generates random package names, which are then continuously republished to pollute the npm registry. The origin of this issue is linked to the broader tea.xyz token reward campaign, which employs such tactics to manipulate npm's reputation system. The ramifications include compromised package integrity, potential security risks for users, and a polluted npm ecosystem.

How To Fix

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

npm uninstall tealove-lady4

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 prevent the installation of the tealove-lady4 package by adding it to your project's .npmrc file with the following line: package-lock=false. This will help avoid any unintended installations of this malicious package.

Conclusion

The tealove-lady4 package poses a significant threat due to its malicious code designed to manipulate the npm ecosystem. It is crucial to take immediate action by uninstalling this package and monitoring your project for any vulnerabilities. Utilizing tools like Vulert can help maintain the security of your application.

See every vulnerability recorded for tealove-lady4 →

Share this vulnerability

FAQ

The tealove-lady4 package is part of a malicious campaign that aims to manipulate npm's reputation system through automated publishing of derivative packages.

The vulnerability can compromise your project's integrity by introducing malicious code that alters package configurations and potentially exposes your application to security risks.

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

There is no patch for the tealove-lady4 package due to its malicious nature. The recommended action is to uninstall the package entirely.

If you have installed the tealove-lady4 package, you should uninstall it immediately using the command npm uninstall tealove-lady4 and review your project for any other potentially malicious packages.

How To Fix

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

npm uninstall tealove-lady4

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