Malicious Code Injection in tealove-reborn2: A Threat to npm Ecosystem
Summary
MAL-2025-168694: Malicious code in tealove-reborn2 (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
tealove-reborn2 is an npm package that is part of the tea.xyz token reward campaign. This package is designed to reward developers with tokens for publishing packages. However, it has been identified as malicious due to its functionality that includes autopublishing scripts which generate and publish derivative packages with randomized names. This behavior is intended to inflate developer reputation scores, leading to potential abuse within the npm ecosystem.
Vulnerability Detail
The vulnerability originates from the malicious code embedded in the tealove-reborn2 package. It modifies the package.json file to remove private flags, alters version numbers, and generates random package names, which can lead to the pollution of the npm registry. This can result in developers unknowingly using compromised packages, which may contain further malicious payloads or lead to reputation damage for legitimate developers.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall tealove-reborn2If 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 remove the tealove-reborn2 package from your project by executing the command: 'npm uninstall tealove-reborn2'. This will prevent any potential exploitation until a secure version is available.
Conclusion
The tealove-reborn2 package poses a significant risk due to its embedded malicious code that can compromise the integrity of npm projects. It is crucial for developers to take immediate action by updating or removing the package and utilizing tools like Vulert to monitor for vulnerabilities in their applications.
See every vulnerability recorded for tealove-reborn2 →
FAQ
tealove-reborn2 is an npm package associated with the tea.xyz token reward campaign, which has been identified as containing malicious code.
The malicious code can modify your package.json, remove private flags, and publish unauthorized packages, potentially compromising your project.
You should uninstall the package immediately and check for any updates or patches that may address the vulnerability.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time using your package-lock.json file. You can also check your application for vulnerabilities using the Vulert playground.
Regularly audit your dependencies, use tools like Vulert for monitoring, and stay informed about known vulnerabilities in the packages you use.
