Malicious Code Injection in teaa-reborn14: A Threat to npm Users
Summary
MAL-2025-166711: Malicious code in teaa-reborn14 (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-reborn14 is an npm package that is part of the tea.xyz token reward campaign, which has been associated with flooding the npm registry with malicious packages. These packages are designed to inflate developer reputation scores through automated scripts that publish derivative packages with randomized names. The primary function of teaa-reborn14 is to facilitate this automated publishing process, but it has been compromised to include malicious code.
Vulnerability Detail
The vulnerability in teaa-reborn14 arises from its inclusion of autopublish scripts that modify the package.json file. This modification removes private flags, alters version numbers, and generates random package names, leading to the continuous republishing of variants that pollute the npm registry. The malicious payload poses a risk to developers by compromising their package integrity and potentially leading to reputational damage.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall teaa-reborn14If 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 remove the teaa-reborn14 package from your project by executing 'npm uninstall teaa-reborn14'. This will prevent any malicious code from executing while you seek a secure alternative.
Conclusion
The teaa-reborn14 package poses a significant risk due to its malicious code that alters package metadata and floods the npm registry. It is crucial for developers to take immediate action by updating or removing the package and utilizing tools like Vulert for ongoing monitoring of vulnerabilities.
See every vulnerability recorded for teaa-reborn14 →
FAQ
teaa-reborn14 is an npm package associated with the tea.xyz token reward campaign, which has been found to contain malicious code.
The malicious code modifies your package.json file, removes private flags, and generates random package names, which can lead to reputational damage and security risks.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check if your application is affected without needing to sign up.
If you have installed teaa-reborn14, you should uninstall it immediately and check for any updates or patches for your other dependencies.
To prevent future vulnerabilities, regularly audit your dependencies, use tools like Vulert for monitoring, and stay updated with the latest security advisories.
