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

tealove-lady20 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-168326: Malicious code in tealove-lady20 (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-lady20 is an npm package that is part of the tea.xyz token reward campaign. This package is designed to interact with the npm ecosystem, allowing developers to publish and manage their packages. However, it has been identified as containing malicious code that can compromise the integrity of the npm registry and the reputation of developers using it.

Vulnerability Detail

The vulnerability in tealove-lady20 originates from its malicious code that modifies the package.json file to remove private flags and change version numbers. It generates random Indonesian-themed package names and continuously republishes variants, leading to pollution of the npm registry. This behavior can inflate developer reputation scores fraudulently and potentially expose users to further malicious packages.

How To Fix

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

npm uninstall tealove-lady20

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-lady20 package by using the following command: npm uninstall tealove-lady20. Additionally, you can monitor your package dependencies using tools like Vulert, which alerts you to open-source vulnerabilities in real-time.

Conclusion

The tealove-lady20 package poses a significant threat due to its malicious code that alters package metadata and affects the npm ecosystem. It is crucial for developers to take immediate action by removing the package and monitoring their projects for vulnerabilities.

See every vulnerability recorded for tealove-lady20 →

Share this vulnerability

FAQ

tealove-lady20 is an npm package associated with the tea.xyz token reward campaign, which has been identified to contain malicious code.

The vulnerability can compromise your project's integrity by allowing malicious code to modify your package.json file and pollute the npm registry.

You should uninstall the package immediately and monitor your dependencies for any further vulnerabilities.

Yes, you can use the Vulert playground to check if your application is affected by this vulnerability without needing to sign up.

Regularly monitor your dependencies using tools like Vulert and keep your packages updated to their latest secure versions.

How To Fix

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

npm uninstall tealove-lady20

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