Malicious Code Injection in teaa-reborn5: npm Package Vulnerability
Summary
MAL-2025-166747: Malicious code in teaa-reborn5 (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-reborn5 is an npm package that is part of the tea.xyz token reward campaign, which has been associated with a series of malicious activities on the npm registry. This package is designed to interact with the npm ecosystem, potentially affecting developers and users who rely on its functionality. The package's primary attributes include automatic publishing scripts that manipulate package metadata, which can lead to unintended consequences for users.
Vulnerability Detail
The vulnerability in teaa-reborn5 stems from its malicious code that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior is part of a broader scheme to inflate developer reputation scores for token rewards, resulting in the continuous republishing of variants that pollute the npm registry. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which has flooded the npm ecosystem with similar malicious packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall teaa-reborn5
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 workaround, you can remove the teaa-reborn5 package from your project by executing the following command: npm uninstall teaa-reborn5. This will prevent any malicious activity associated with the package until a fix is applied.
Conclusion
The teaa-reborn5 package presents a significant vulnerability due to its malicious code that alters package metadata and inflates developer reputation scores. It is crucial for developers to take immediate action by updating or uninstalling the package to protect their projects from potential harm.
See every vulnerability recorded for teaa-reborn5 →
FAQ
teaa-reborn5 is an npm package associated with the tea.xyz token reward campaign, which has been found to contain malicious code.
The vulnerability can lead to unauthorized modifications of your package.json file, potentially exposing your project to further risks and pollution of the npm registry.
Check the package's repository for any updates or patches that address this vulnerability. If a patched version is available, updating the package is essential.
You can use tools like Vulert, which monitors your package-lock.json for open-source vulnerabilities in real-time without requiring code access or installation.
If you cannot update the package, consider uninstalling it as a temporary measure to mitigate the risk until a fix is available.