Malicious Code Injection in teaa-reborn44: A Threat to npm Ecosystem

teaa-reborn44 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-166741: Malicious code in teaa-reborn44 (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

teaa-reborn44 is an npm package that is part of the tea.xyz token reward campaign. This package is designed to facilitate the distribution of token rewards through various scripts. However, it has been identified as containing malicious code that compromises the integrity of the npm registry by generating and publishing derivative packages with altered metadata.

Vulnerability Detail

The vulnerability in teaa-reborn44 arises from its malicious payload, which modifies the package.json file to remove private flags and changes version numbers. It generates random package names, often themed around Indonesian culture, and continuously republishes these variants to inflate developer reputation scores. This behavior not only pollutes the npm registry but also poses a risk to developers who may unknowingly install these compromised packages.

How To Fix

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

npm uninstall teaa-reborn44

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, you can avoid using teaa-reborn44 and any other packages associated with the tea.xyz token reward campaign. Regularly audit your dependencies using tools like npm audit to identify and mitigate risks from malicious packages.

Conclusion

The teaa-reborn44 package poses a significant threat to the npm ecosystem due to its malicious code that alters package metadata and floods the registry with derivative packages. It is crucial for developers to remove this package and monitor their dependencies for vulnerabilities to maintain the integrity of their projects.

See every vulnerability recorded for teaa-reborn44 →

Share this vulnerability

FAQ

teaa-reborn44 is an npm package involved in the tea.xyz token reward campaign, which has been found to contain malicious code.

The malicious code modifies your package.json file, removes private flags, and creates numerous derivative packages that can clutter the npm registry and potentially introduce security risks.

You can use Vulert to monitor your package-lock.json for vulnerabilities. Visit Vulert Scanner to check if your application is affected without any signup.

If you have installed teaa-reborn44, it is advisable to remove it from your project immediately and audit your dependencies for any other potential vulnerabilities.

Yes, tools like npm audit and Vulert can help you identify and manage vulnerabilities in your npm packages effectively.

How To Fix

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

npm uninstall teaa-reborn44

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