Malicious Code Injection in tealove-reborn32 Package - npm Vulnerability
Summary
MAL-2025-168708: Malicious code in tealove-reborn32 (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 tealove-reborn32 package 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. This behavior compromises the integrity of the npm ecosystem and poses a risk to developers using these packages.
Vulnerability Detail
The vulnerability in the tealove-reborn32 package is characterized by the presence of malicious code that modifies the package.json file. This code removes private flags, alters version numbers, and generates random package names, leading to the continuous republishing of these variants. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which aims to manipulate npm's reputation system. The ramifications include pollution of the npm registry and potential security risks for developers who inadvertently use these compromised packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall tealove-reborn32If 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-reborn32 package and look for alternative packages that provide similar functionality without the associated risks. 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 tealove-reborn32 package poses a significant risk due to its malicious code designed to manipulate npm's reputation system. Developers should take immediate action to remove this package and monitor their projects for vulnerabilities using tools like Vulert. Staying informed and proactive is crucial in maintaining the security of your applications.
See every vulnerability recorded for tealove-reborn32 →
FAQ
Tealove-reborn32 is an npm package that is part of a campaign to manipulate developer reputation scores through the automatic generation of malicious packages.
The vulnerability can lead to the pollution of the npm registry and may introduce security risks if your project inadvertently uses compromised packages.
You should remove the tealove-reborn32 package from your project and monitor for any updates or patches that may address this vulnerability.
You can use tools like Vulert, which monitors your package-lock.json file to alert you in real-time for open-source vulnerabilities.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.
