Malicious Code Injection in teaa-reborn28: A Threat to npm Users
Summary
MAL-2025-166724: Malicious code in teaa-reborn28 (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-reborn28 is an npm package that is part of the tea.xyz token reward campaign, which has been known to flood the npm registry with malicious packages. These packages are designed to manipulate developer reputation scores by automatically generating and publishing derivative packages with randomized names. The vulnerability in teaa-reborn28 allows for the modification of package.json files, leading to potential security risks for users relying on this package.
Vulnerability Detail
The vulnerability originates from the malicious intent behind the teaa-reborn28 package, which includes scripts that automatically modify package.json files. These modifications remove private flags, alter version numbers, and generate random package names, leading to the continuous republishing of variants. This behavior not only pollutes the npm registry but also poses a risk to developers who may unknowingly use these compromised packages, potentially exposing their applications to further vulnerabilities.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall teaa-reborn28If 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 teaa-reborn28 and any other packages associated with the tea.xyz token reward campaign. Additionally, consider using tools like Vulert to monitor your package-lock.json 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-reborn28 package poses a significant risk due to its malicious code that modifies package files and repopulates the npm registry with compromised versions. Users are advised to remove this package and utilize tools like Vulert for ongoing monitoring of their dependencies to safeguard their applications.
See every vulnerability recorded for teaa-reborn28 →
FAQ
teaa-reborn28 is an npm package involved in a token reward campaign that has been identified as malicious due to its behavior of modifying package files.
The vulnerability can lead to the injection of malicious code into your application, potentially compromising its security and integrity.
You should remove the teaa-reborn28 package from your project and monitor your dependencies for any further vulnerabilities.
Yes, regularly audit your dependencies, use tools like Vulert for real-time monitoring, and stay informed about known vulnerabilities in the packages you use.
Yes, you can use the Vulert playground at Vulert Scanner to check your application for vulnerabilities by simply uploading your package-lock.json.
