Malicious Code Injection in tealove-reborn49: A Threat to npm Ecosystem

tealove-reborn49 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-168726: Malicious code in tealove-reborn49 (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 Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

tealove-reborn49 is an npm package that is part of the tea.xyz token reward campaign. This package is designed to interact with the npm registry, allowing developers to publish and manage their packages. However, it has been identified as malicious due to its functionality that includes autopublishing scripts which generate and publish derivative packages with randomized names, aimed at inflating developer reputation scores for token rewards.

Vulnerability Detail

The vulnerability in tealove-reborn49 stems from its malicious payload that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior leads to the continuous republishing of variants, polluting the npm registry and potentially compromising the integrity of the ecosystem. The origin of this issue is linked to the tea.xyz token reward campaign, which incentivizes such malicious practices.

How To Fix

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

npm uninstall tealove-reborn49

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

There are no direct workarounds to mitigate the effects of this malicious package. The best approach is to completely remove it from your project and avoid using any packages associated with the tea.xyz token reward campaign.

Conclusion

The tealove-reborn49 package poses a significant threat to the npm ecosystem due to its malicious code that alters package metadata and floods the registry with unwanted variants. It is essential for developers to remain vigilant and utilize tools like Vulert to monitor their dependencies for vulnerabilities.

See every vulnerability recorded for tealove-reborn49 →

Share this vulnerability

FAQ

tealove-reborn49 is an npm package associated with the tea.xyz token reward campaign, which has been identified as containing malicious code.

The malicious code modifies your package.json file, removes private flags, and generates random package names, which can lead to pollution of the npm registry and compromise your project's integrity.

You should uninstall the package immediately using the command 'npm uninstall tealove-reborn49' to prevent any potential harm to your project.

While many packages in the npm ecosystem are safe, it is crucial to vet packages before installation. Use tools like Vulert to monitor and alert for vulnerabilities in your dependencies.

You can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.

How To Fix

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

npm uninstall tealove-reborn49

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