Malicious Code Injection in teaa-reborn46: A Threat to npm Packages

teaa-reborn46 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

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

teaa-reborn46 is an npm package that is part of a token reward campaign associated with the tea.xyz protocol. This package is designed to facilitate the automatic generation and publication of derivative packages, which can inflate developer reputation scores for rewards. However, it has been identified as containing malicious code that compromises the integrity of the npm ecosystem.

Vulnerability Detail

The vulnerability in teaa-reborn46 originates from its design to include autopublish scripts that modify the package.json file. These modifications remove private flags, alter version numbers, and generate random package names, leading to the continuous republishing of variants that pollute the npm registry. This behavior not only affects the reputation of developers but also poses a risk of introducing malicious packages to users who may unknowingly install them.

How To Fix

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

npm uninstall teaa-reborn46

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, avoid using teaa-reborn46 and any packages that depend on it. Regularly audit your package-lock.json file to identify and remove any potentially malicious packages. You can also use tools like Vulert to monitor your project for vulnerabilities without requiring code access.

Conclusion

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

See every vulnerability recorded for teaa-reborn46 →

Share this vulnerability

FAQ

teaa-reborn46 is an npm package involved in a token reward campaign that automates the generation and publication of derivative packages.

The vulnerability can lead to the introduction of malicious packages into your project, compromising its security and integrity.

You should uninstall the package immediately using 'npm uninstall teaa-reborn46' and check your project for any other affected packages.

Yes, you can use Vulert to monitor your project in real-time for open-source vulnerabilities by analyzing your package-lock.json file.

You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.

How To Fix

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

npm uninstall teaa-reborn46

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