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

tealove-lady13 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-168318: Malicious code in tealove-lady13 (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-lady13 is part of the tea.xyz token reward campaign, which has been known to flood the npm registry with malicious packages. These packages are designed to manipulate developer reputation scores by automatically generating and publishing derivative packages with randomized names. This behavior not only affects the integrity of the npm ecosystem but also poses a significant risk to developers who may unknowingly use these compromised packages.

Vulnerability Detail

The vulnerability in tealove-lady13 stems from its malicious payload that modifies the package.json file by removing private flags and altering version numbers. It generates random Indonesian-themed package names and continuously republishes variants, polluting the npm registry. This behavior can lead to developers inadvertently using compromised packages, which may contain further vulnerabilities or malicious code, ultimately compromising their applications.

How To Fix

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

npm uninstall tealove-lady13

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 measure, you can avoid using the tealove-lady13 package and monitor your package-lock.json for any unauthorized changes. Regularly audit your dependencies using npm audit to identify and address vulnerabilities.

Conclusion

The tealove-lady13 package poses a significant threat to the npm ecosystem due to its malicious behavior. Developers should take immediate action to remove this package and monitor their dependencies for vulnerabilities. Utilizing tools like Vulert can aid in maintaining the security of your applications.

See every vulnerability recorded for tealove-lady13 →

Share this vulnerability

FAQ

Tealove-lady13 is an npm package that has been identified as malicious, designed to manipulate developer reputation scores through automated publishing of derivative packages.

The vulnerability can lead to the inclusion of compromised packages in your application, which may contain malicious code or further vulnerabilities, jeopardizing the security of your software.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. By checking your package-lock.json, you can determine if your application is affected by this vulnerability.

Immediately uninstall the package using 'npm uninstall tealove-lady13' and audit your project for any other potentially compromised dependencies.

Yes, Vulert provides a playground where you can check for vulnerabilities in your application without requiring access to the code or installation. Visit Vulert Scanner to use the tool.

How To Fix

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

npm uninstall tealove-lady13

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