Malicious Code Injection in teaa-reborn6: A Threat to npm Users
Summary
MAL-2025-166749: Malicious code in teaa-reborn6 (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
teaa-reborn6 is an npm package that appears to be part of a token reward campaign associated with the tea.xyz protocol. It is designed to incentivize developers through token rewards by manipulating the npm registry. The package's functionality includes generating and publishing derivative packages with randomized names, which can inflate developer reputation scores. However, this behavior poses significant risks to the integrity of the npm ecosystem.
Vulnerability Detail
The vulnerability in teaa-reborn6 stems from the presence of malicious code that modifies the package.json file. This code removes private flags, alters version numbers, and generates random package names, leading to the continuous republishing of variants. The primary origin of this issue is linked to the package's involvement in the tea.xyz token reward campaign, which aims to manipulate npm's reputation system. The ramifications include potential pollution of the npm registry, increased security risks for developers using these packages, and a compromised development environment.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall teaa-reborn6If 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 the teaa-reborn6 package altogether and look for alternative packages that provide similar functionality without the associated risks. Additionally, you can implement strict package auditing practices in your development workflow to identify and mitigate vulnerabilities.
Conclusion
The teaa-reborn6 package poses a significant threat due to its malicious code that manipulates the npm registry. It is crucial for developers to remove this package from their projects and adopt best practices for monitoring and managing dependencies to ensure the security of their applications.
See every vulnerability recorded for teaa-reborn6 →
FAQ
teaa-reborn6 is an npm package involved in a token reward campaign that manipulates the npm registry by generating and publishing derivative packages.
The vulnerability can lead to the pollution of the npm registry and increase security risks, potentially compromising your development environment.
You should uninstall the package immediately using npm uninstall teaa-reborn6 and monitor your project for any other vulnerabilities.
Yes, tools like Vulert can monitor your package-lock.json file to alert you in real-time about open-source vulnerabilities without requiring code access.
You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.
