Malicious Code Injection in tealove1111: A Threat to npm Users
Summary
MAL-2025-168733: Malicious code in tealove1111 (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 tealove1111 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 presence of such packages poses a significant risk to users and the integrity of the npm registry.
Vulnerability Detail
The vulnerability in tealove1111 originates from its malicious payload that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior leads to the continuous republishing of variants, which pollutes the npm registry and can compromise the security and reliability of applications relying on these packages. The automated scripts (auto.js, autopublish.js, etc.) are specifically designed to exploit the npm ecosystem for token rewards.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall tealove1111If 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 tealove1111 package and any packages that depend on it. Additionally, consider using tools like Vulert to monitor your project for vulnerabilities. You can check if your application is affected by this vulnerability using the Vulert playground at https://vulert.com/scanner without any signup.
Conclusion
The tealove1111 package poses a significant risk due to its malicious code designed to exploit the npm ecosystem. Users are advised to uninstall this package and monitor their projects for vulnerabilities using tools like Vulert. Staying informed and proactive is essential to maintaining the security of your applications.
See every vulnerability recorded for tealove1111 →
FAQ
Tealove1111 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 injection of malicious code into your application, potentially compromising its security and functionality.
You should uninstall the tealove1111 package immediately using the command npm uninstall tealove1111 and check for any dependencies that may rely on it.
You can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities in your software by analyzing your package-lock.json file.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by vulnerabilities without requiring any signup.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
