Malicious Code Injection in teaa-reborn29: A Threat to npm Packages
Summary
MAL-2025-166725: Malicious code in teaa-reborn29 (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
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
Background
teaa-reborn29 is an npm package that appears to be part of the tea.xyz token reward campaign. This package is designed to facilitate the automatic generation and publication of derivative packages, which are often used to inflate developer reputation scores for token rewards. The package's functionality is compromised due to its malicious intent, leading to potential pollution of the npm registry.
Vulnerability Detail
The vulnerability in teaa-reborn29 originates from its inclusion in a campaign that floods the npm ecosystem with malicious packages. The malicious payload modifies the package.json file by removing private flags, altering version numbers, and generating random package names, which can lead to the proliferation of untrustworthy packages in the npm registry. This not only affects the integrity of the npm ecosystem but also poses a risk to developers who may unknowingly use these compromised packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall teaa-reborn29If 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 workaround, you can avoid using the teaa-reborn29 package altogether and consider using alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your package dependencies using tools like Vulert, which can alert you to open-source vulnerabilities in your software.
Conclusion
The teaa-reborn29 package poses a significant risk due to its malicious code designed to manipulate the npm registry. It is crucial for developers to remove this package and monitor their dependencies for vulnerabilities to maintain the integrity of their projects.
See every vulnerability recorded for teaa-reborn29 →
FAQ
teaa-reborn29 is an npm package involved in a token reward campaign that generates and publishes derivative packages to inflate developer reputation scores.
The vulnerability can lead to the pollution of the npm registry, potentially exposing your project to untrustworthy packages and compromising its integrity.
You should remove the teaa-reborn29 package from your project and monitor for any updates or patches that may address the vulnerability.
You can use tools like Vulert, which allows you to monitor and receive alerts for open-source vulnerabilities in your software without requiring access to the code or installation.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
