Malicious Code Injection in tealove-lady7: npm Package Vulnerability

tealove-lady7 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

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

The tealove-lady7 package is part of the tea.xyz token reward campaign, which has been known to flood the npm ecosystem with malicious packages. These packages are designed to manipulate developer reputation scores for token rewards by automatically generating and publishing derivative packages with randomized names. The functionality of this package is compromised due to its malicious intent, posing significant risks to developers and their projects.

Vulnerability Detail

The vulnerability in tealove-lady7 originates from its inclusion in a campaign that employs autopublish scripts to create and publish numerous derivative packages. These scripts modify the package.json file by removing private flags, altering version numbers, and generating random package names, which leads to pollution of the npm registry. This not only affects the integrity of the npm ecosystem but also exposes developers to potential security risks and reputation damage.

How To Fix

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

npm uninstall tealove-lady7

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 workaround, you can avoid using the tealove-lady7 package and monitor your project's dependencies for any malicious packages. You can also utilize tools like Vulert to monitor and alert you for open-source vulnerabilities in your software. For real-time monitoring, you can check your application against this vulnerability using the Vulert playground at https://vulert.com/scanner without any signup.

Conclusion

The tealove-lady7 package poses a significant threat due to its malicious code designed to manipulate npm package publishing. Developers should take immediate action to remove this package and utilize tools like Vulert for ongoing monitoring of vulnerabilities in their projects.

See every vulnerability recorded for tealove-lady7 →

Share this vulnerability

FAQ

Tealove-lady7 is an npm package that is part of a malicious campaign aimed at manipulating developer reputation scores for token rewards.

The vulnerability can lead to the pollution of the npm registry and expose your project to security risks, as well as damage your reputation as a developer.

You should remove the tealove-lady7 package from your project immediately and monitor for any updates or patches.

You can use tools like Vulert, which monitors your package-lock.json for vulnerabilities in real-time without requiring code access or installation.

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

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-lady7

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