Malicious Code Injection in tealove-reborn36: A Threat to npm Users
Summary
MAL-2025-168712: Malicious code in tealove-reborn36 (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-reborn36 is an npm package that is part of the tea.xyz token reward campaign. It is designed to facilitate token rewards for developers by generating and publishing derivative packages. However, this package has been identified as malicious, containing scripts that manipulate its own package metadata and flood the npm registry with harmful variants.
Vulnerability Detail
The vulnerability in tealove-reborn36 stems from its inclusion in a malicious campaign that utilizes autopublish scripts to create and publish numerous derivative packages with altered metadata. These scripts modify the package.json file to remove private flags, change version numbers, and generate random package names, ultimately leading to the pollution of the npm registry. This can result in compromised developer reputations and potential security risks for users who inadvertently install these malicious packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall tealove-reborn36If 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-reborn36 package and monitor your dependencies for any malicious activity. Additionally, consider using tools like Vulert to keep track of vulnerabilities in your project. 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-reborn36 package poses a significant risk due to its malicious code designed to manipulate package metadata and flood the npm registry. It is crucial for developers to remove this package from their projects and utilize tools like Vulert to monitor for vulnerabilities in their dependencies.
See every vulnerability recorded for tealove-reborn36 →
FAQ
tealove-reborn36 is an npm package associated with the tea.xyz token reward campaign, which has been identified as containing malicious code.
The malicious code can alter your package metadata, remove private flags, and flood the npm registry with harmful variants, potentially compromising your project's integrity.
You should uninstall the package immediately using the command 'npm uninstall tealove-reborn36' to mitigate any risks.
You can use tools like Vulert, which monitors your package-lock.json for vulnerabilities in real-time without requiring code access or installation.
Yes, you can use the Vulert playground at Vulert Scanner to check for vulnerabilities in your application without signing up.
