Malicious Code Injection in tealove-reborn46: A Threat to npm Packages
Summary
MAL-2025-168723: Malicious code in tealove-reborn46 (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-reborn46 is an npm package that is part of the tea.xyz token reward campaign. This package is designed to interact with the npm registry, and its primary functionality revolves around generating and publishing derivative packages. However, it has been identified as malicious due to its capability to manipulate package metadata and publish harmful variants, which can compromise the integrity of the npm ecosystem.
Vulnerability Detail
The vulnerability in tealove-reborn46 stems from its inclusion in a malicious campaign that floods the npm registry with derivative packages. The package contains scripts that automatically modify the package.json file to remove private flags, alter version numbers, and generate random package names. This behavior not only inflates developer reputation scores for token rewards but also pollutes the npm registry with potentially harmful packages, posing a risk to developers who may unknowingly install these variants.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall tealove-reborn46If 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
If you cannot update the package immediately, consider removing tealove-reborn46 from your project to prevent any potential exploitation. You can do this by executing the following command: npm uninstall tealove-reborn46.
Conclusion
The tealove-reborn46 package poses a significant risk due to its malicious code that alters package metadata and floods the npm registry with harmful variants. It is crucial for developers to stay vigilant, update their dependencies, and utilize tools like Vulert to monitor for vulnerabilities effectively.
See every vulnerability recorded for tealove-reborn46 →
FAQ
tealove-reborn46 is an npm package involved in a token reward campaign that has been identified as malicious due to its harmful scripts.
The vulnerability can lead to the injection of malicious code, modification of package metadata, and the potential installation of harmful packages in your project.
You should update the package to the latest version or uninstall it to mitigate the risk of exploitation.
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 if your application is affected by this vulnerability without signing up.
