Malicious Code Vulnerability in teaa-reborn25: Exploitation of npm Packages for Token Rewards

teaa-reborn25 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-166722: Malicious code in teaa-reborn25 (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-reborn25 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 by generating and publishing derivative packages. It has been identified as part of a broader trend of malicious packages that aim to inflate developer reputation scores through automated publishing scripts.

Vulnerability Detail

The vulnerability in teaa-reborn25 originates from its malicious code that modifies the package.json file to remove private flags and alters version numbers. It generates random package names, often themed around Indonesian culture, and continuously republishes these variants to pollute the npm registry. This behavior not only compromises the integrity of the npm ecosystem but also poses risks to developers who may unknowingly use these compromised packages, leading to potential security breaches and loss of trust in the package management system.

How To Fix

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

npm uninstall teaa-reborn25

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 workaround, you can monitor your package dependencies using tools like Vulert, which can alert you in real-time for open-source vulnerabilities. You can check if your application is affected by this vulnerability using the Vulert playground at https://vulert.com/scanner without any signup.

Conclusion

The teaa-reborn25 package has been identified as containing malicious code that compromises the integrity of the npm ecosystem. It is crucial for developers to remove this package and monitor their dependencies for vulnerabilities to maintain the security of their applications.

See every vulnerability recorded for teaa-reborn25 →

Share this vulnerability

FAQ

teaa-reborn25 is an npm package associated with the tea.xyz token reward campaign, designed to automate the generation and publication of derivative packages.

The vulnerability allows malicious code to modify your package.json, potentially leading to the installation of compromised packages and security risks.

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

You can use tools like Vulert, which monitors your package-lock.json for vulnerabilities and alerts you in real-time.

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by 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-reborn25

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