Malicious Code Injection in tealove-lady30: npm Package Vulnerability
Summary
MAL-2025-168337: Malicious code in tealove-lady30 (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
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
Background
The package tealove-lady30 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 inflate developer reputation scores through automated scripts that generate and publish derivative packages with randomized names. The primary functionality of tealove-lady30 is to serve as a token reward mechanism, but its malicious behavior compromises the integrity of the npm registry.
Vulnerability Detail
The vulnerability in tealove-lady30 originates from its inclusion in a campaign that utilizes autopublish scripts (such as auto.js, autopublish.js, autopublish2.js, autopublish3.js) to modify package.json files. This modification removes private flags, alters version numbers, and generates random package names, leading to the continuous republishing of variants that pollute the npm registry. The ramifications include potential security risks for developers who unknowingly install these malicious packages, as well as the degradation of the npm ecosystem's reliability.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall tealove-lady30If 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 avoid using the tealove-lady30 package and monitor your project for any dependencies that may inadvertently include it. Additionally, consider using tools like Vulert to monitor your package-lock.json for vulnerabilities.
Conclusion
The tealove-lady30 package poses a significant risk due to its malicious code designed to manipulate the npm registry. It is crucial for developers to remove this package and monitor their projects for similar vulnerabilities. Utilizing tools like Vulert can help maintain the security of your applications.
See every vulnerability recorded for tealove-lady30 →
FAQ
tealove-lady30 is an npm package that is part of a malicious campaign aimed at inflating developer reputation scores through automated publishing.
The vulnerability can lead to the installation of malicious code, which may compromise your project's security and integrity.
You should uninstall the package immediately using the command npm uninstall tealove-lady30.
Yes, you can use Vulert to monitor your package-lock.json for real-time alerts on open-source vulnerabilities.
You can use the Vulert playground at Vulert Scanner to check if your application is affected without needing to sign up.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
