Malicious Code Injection in teaa-reborn34: Exploiting npm for Token Rewards

teaa-reborn34 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-166731: Malicious code in teaa-reborn34 (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 Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

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

Vulnerability Detail

The vulnerability in teaa-reborn34 stems from its malicious payload, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior is intended to continuously republish variants of the package, polluting the npm registry and potentially leading to reputation damage for developers and security risks for users who unknowingly install these compromised packages. The source of this vulnerability is linked to the tea.xyz token reward campaign, which has been identified as a source of malicious npm packages.

How To Fix

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

npm uninstall teaa-reborn34

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 measure, avoid using the teaa-reborn34 package and monitor your dependencies for any malicious activity. You can also use tools like Vulert to check your package-lock.json for vulnerabilities. To check if your application is affected by this vulnerability, visit the Vulert playground at https://vulert.com/scanner without any signup.

Conclusion

The teaa-reborn34 package has been identified as containing malicious code that poses a significant risk to developers and users alike. It is crucial to remove this package from your projects and monitor your dependencies for any potential vulnerabilities. Utilizing tools like Vulert can help ensure your applications remain secure.

See every vulnerability recorded for teaa-reborn34 →

Share this vulnerability

FAQ

teaa-reborn34 is an npm package associated with the tea.xyz token reward campaign, designed to generate and publish derivative packages.

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

You should uninstall the package immediately using the command npm uninstall teaa-reborn34.

Yes, you can use Vulert to monitor your package-lock.json for real-time alerts on open-source vulnerabilities.

Yes, you can use the Vulert playground at Vulert Scanner to check for vulnerabilities without requiring any signup.

How To Fix

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

npm uninstall teaa-reborn34

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