Malicious Code Vulnerability in tealove-reborn43: Exploiting npm Packages for Token Rewards
Summary
MAL-2025-168720: Malicious code in tealove-reborn43 (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-reborn43 is an npm package that is part of the tea.xyz token reward campaign. This package is designed to facilitate the generation and publication of derivative packages. However, it has been identified as malicious due to its functionality that inflates developer reputation scores through automated scripts.
Vulnerability Detail
The vulnerability in tealove-reborn43 originates from its inclusion in a campaign that floods the npm registry with malicious packages. These packages contain scripts that modify the package.json file to remove private flags, change version numbers, and generate random package names. This behavior leads to the pollution of the npm registry and can compromise the integrity of other packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall tealove-reborn43If 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 manually remove the tealove-reborn43 package from your project by running: npm uninstall tealove-reborn43. Additionally, consider using tools like Vulert to monitor your package dependencies for vulnerabilities.
Conclusion
The tealove-reborn43 package poses a significant risk due to its malicious code designed to manipulate npm package metadata. It is crucial to remove this package and monitor your dependencies for vulnerabilities to maintain the integrity of your projects.
See every vulnerability recorded for tealove-reborn43 →
FAQ
The vulnerability involves malicious scripts that modify package metadata and flood the npm registry with derivative packages.
You can use Vulert's playground at Vulert Scanner to check your application for vulnerabilities without needing to sign up.
Using this package can lead to the pollution of the npm registry and may compromise the security and integrity of your project.
Regularly audit your dependencies and utilize tools like Vulert to monitor for vulnerabilities in real-time.
Remove the package immediately and check for any other dependencies that may have been affected by its malicious behavior.
