Malicious Code Exploit in tealove-reborn39: A Threat to npm Packages
Summary
MAL-2025-168715: Malicious code in tealove-reborn39 (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
tealove-reborn39 is an npm package that is part of the tea.xyz token reward campaign. This package is designed to facilitate token rewards for developers by generating and publishing derivative packages. However, it has been identified as containing malicious code that compromises the integrity of the npm registry.
Vulnerability Detail
The vulnerability in tealove-reborn39 originates from its malicious payload, which modifies the package.json file to remove private flags and alters version numbers. It generates random package names, often themed around Indonesian culture, and continuously republishes these variants to pollute the npm registry. This behavior can inflate developer reputation scores fraudulently and lead to a compromised ecosystem where malicious packages proliferate.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall tealove-reborn39If 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-reborn39 package from your project by executing the following command: npm uninstall tealove-reborn39. This will prevent any malicious code from executing while you assess your project's dependencies.
Conclusion
The tealove-reborn39 package poses a significant threat due to its malicious code that alters package metadata and floods the npm registry with fraudulent packages. It is crucial for developers to remain vigilant, update their dependencies, and utilize tools like Vulert to monitor for vulnerabilities.
See every vulnerability recorded for tealove-reborn39 →
FAQ
The vulnerability involves malicious code that modifies package metadata and republishes variants to the npm registry, potentially compromising the integrity of the ecosystem.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. By uploading your package-lock.json file to the Vulert playground, you can check for vulnerabilities without needing to install any software.
Using tealove-reborn39 can lead to the proliferation of malicious packages in your project, which may compromise your application's security and integrity.
Regularly updating your dependencies, using tools like Vulert for monitoring vulnerabilities, and auditing your package.json and package-lock.json files can help prevent such issues.
It is advisable to uninstall the package immediately and review your project's dependencies for any other potentially malicious packages.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
