Malicious Code Injection in teaa-reborn8 Package: npm Vulnerability Overview
Summary
MAL-2025-166751: Malicious code in teaa-reborn8 (npm). Affected versions are not published. No fix is published. How to fix ↓
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.
No signup required · Results in about 60 seconds
Background
The teaa-reborn8 package is part of a broader campaign associated with the tea.xyz token reward system, which has been known to flood the npm ecosystem with malicious packages. These packages are designed to manipulate developer reputation scores by automatically generating and publishing derivative packages with randomized names. The functionality of teaa-reborn8 is compromised due to its embedded malicious code, which alters package metadata and continuously republishes variants to the npm registry.
Vulnerability Detail
The vulnerability in the teaa-reborn8 package originates from its design to include autopublish scripts that modify the package.json file. This modification removes private flags, alters version numbers, and generates random package names, leading to the pollution of the npm registry. The ramifications of this vulnerability include potential security risks for developers who unknowingly install these malicious packages, as well as damage to the integrity of the npm ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall teaa-reborn8If 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 prevent the installation of the teaa-reborn8 package by using npm's package-lock.json to monitor dependencies. Ensure that your project does not include this package by checking your package.json and removing any references to it.
Conclusion
The teaa-reborn8 package poses a significant risk due to its malicious code designed to manipulate npm package metadata. It is essential to remove this package from your project and monitor your dependencies to maintain the integrity and security of your applications.
See every vulnerability recorded for teaa-reborn8 →
FAQ
teaa-reborn8 is an npm package associated with the tea.xyz token reward campaign, known for flooding the npm registry with malicious packages.
The vulnerability can lead to the installation of malicious code that modifies your project's package metadata and can compromise your application's security.
You should immediately remove the teaa-reborn8 package from your project and check for any unauthorized changes in your package.json file.
Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time using your package-lock.json file. You can check your application for vulnerabilities without any signup at the Vulert playground.
Regularly audit your dependencies, use tools like Vulert for monitoring, and stay informed about known vulnerabilities in the packages you use.
