Malicious Code Injection in teaa-reborn38 Package: A Threat to npm Users
Summary
MAL-2025-166735: Malicious code in teaa-reborn38 (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-reborn38 package is part of the tea.xyz token reward campaign that has infiltrated the npm ecosystem. It is designed to facilitate token rewards through the generation of derivative packages. This package, like others in the campaign, is characterized by its use of autopublish scripts that automatically create and publish numerous variants of itself, often with randomized names, to enhance developer reputation scores for token rewards. However, this functionality has been exploited to introduce malicious behavior.
Vulnerability Detail
The vulnerability in the teaa-reborn38 package stems from its malicious payload, which modifies the package.json file by removing private flags, altering version numbers, and generating random package names. This behavior not only pollutes the npm registry but also poses a risk to developers who may unknowingly install these compromised packages. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which aims to inflate developer reputation scores through deceptive practices.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall teaa-reborn38If 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-reborn38 package and any other packages associated with the tea.xyz token reward campaign. Additionally, consider using tools like Vulert to monitor your project for 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-reborn38 package poses a significant risk due to its malicious behavior, which can compromise your project's integrity. It is essential to remove this package and monitor your dependencies for vulnerabilities. Utilizing tools like Vulert can help you stay informed about potential threats in your open-source software.
See every vulnerability recorded for teaa-reborn38 →
FAQ
The teaa-reborn38 package is part of a campaign that generates derivative npm packages to inflate developer reputation scores for token rewards.
The malicious code modifies your package.json file, removes private flags, and publishes random package variants, potentially leading to security risks and pollution of the npm registry.
You can check your package-lock.json file or use npm list to see if teaa-reborn38 is listed as a dependency in your project.
You should remove the teaa-reborn38 package from your project immediately and monitor for any updates or patches.
Yes, Vulert can monitor your project for open-source vulnerabilities in real-time using just your package-lock.json file. You can check for vulnerabilities at Vulert Scanner.
