Malicious Code Injection in tealove-reborn1: A Threat to npm Users

tealove-reborn1 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-168683: Malicious code in tealove-reborn1 (npm). Affected versions are not published. No fix is published. How to fix ↓

Free scan

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.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

tealove-reborn1 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, often with randomized names, to inflate developer reputation scores for tea protocol token rewards. The package's functionality is compromised by malicious scripts that manipulate its metadata.

Vulnerability Detail

The vulnerability in tealove-reborn1 stems from its inclusion in a malicious campaign that utilizes autopublish scripts to modify the package.json file. This modification removes private flags, alters version numbers, and generates random package names, leading to the continuous republishing of variants that pollute the npm registry. The ramifications include potential security risks for users who may inadvertently install these malicious packages, as well as damage to the integrity of the npm ecosystem.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall tealove-reborn1

If 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, users can avoid using the tealove-reborn1 package until a secure version is released. Additionally, consider using alternative packages that provide similar functionality without the associated risks.

Conclusion

The tealove-reborn1 package poses a significant security risk due to its malicious code designed to manipulate package metadata. Users are advised to update or remove the package and utilize monitoring tools like Vulert to stay informed about potential vulnerabilities in their applications.

See every vulnerability recorded for tealove-reborn1 →

Share this vulnerability

FAQ

tealove-reborn1 is an npm package involved in the tea.xyz token reward campaign, which aims to inflate developer reputation scores.

The vulnerability can lead to the installation of malicious packages that may compromise your application's security and integrity.

If you have installed tealove-reborn1, it is recommended to remove it and update to a patched version or use an alternative package.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time using just package-lock.json. You can check your application for vulnerabilities using the Vulert playground at Vulert Scanner.

Regularly updating your packages, using trusted sources, and employing tools like Vulert can help prevent vulnerabilities in your applications.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall tealove-reborn1

If 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 →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback