Malicious Code Vulnerability in tealove-lady2: Exploitation of npm Packages
Summary
MAL-2025-168325: Malicious code in tealove-lady2 (npm). Affected versions are not published. No fix is published. How to fix ↓
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.
No signup required · Results in about 60 seconds
Background
The package tealove-lady2 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 inflate developer reputation scores by automatically generating and publishing derivative packages with randomized names. The functionality of tealove-lady2 is compromised due to its malicious intent, which involves altering package metadata and continuously republishing variants.
Vulnerability Detail
The vulnerability in tealove-lady2 stems from its inclusion in a malicious campaign that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior leads to the pollution of the npm registry and can significantly impact developers by inflating reputation scores fraudulently. The malicious payload is executed through scripts that automate the publishing process, making it difficult for developers to detect and mitigate the issue.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall tealove-lady2
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 remove the tealove-lady2 package from your project by executing the following command: npm uninstall tealove-lady2. This will prevent any malicious code from executing in your application.
Conclusion
The tealove-lady2 package poses a significant security risk due to its malicious code designed to manipulate npm package metadata. It is crucial for developers to take immediate action by uninstalling the package and monitoring their applications for vulnerabilities. Utilizing tools like Vulert can aid in maintaining the security of your software.
See every vulnerability recorded for tealove-lady2 →
FAQ
Tealove-lady2 is an npm package that is part of a malicious campaign aimed at inflating developer reputation scores through automated publishing of derivative packages.
The vulnerability can lead to the pollution of the npm registry and may compromise the integrity of your application by introducing malicious code.
You should uninstall the package immediately and check for any other affected packages in your project.
Yes, you can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities using just your package-lock.json file.
You can use the Vulert playground at Vulert Scanner to check if your application is affected without requiring any signup.