Malicious Code Injection in teaa-reborn30 Package
Summary
MAL-2025-166727: Malicious code in teaa-reborn30 (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
The teaa-reborn30 package is part of the tea.xyz token reward campaign that has recently flooded the npm ecosystem. This package is designed to facilitate the automatic generation and publication of derivative packages, which can inflate developer reputation scores for rewards. However, it has been identified as containing malicious code that compromises the integrity of the npm registry.
Vulnerability Detail
The vulnerability in the teaa-reborn30 package originates from its malicious payload, which modifies the package.json file to remove private flags and alters version numbers. It generates random package names, primarily themed around Indonesian culture, and continuously republishes these variants to pollute the npm registry. This behavior can lead to significant reputational damage for developers and can compromise the security of applications relying on this package.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall teaa-reborn30If 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-reborn30 package altogether. If you have dependencies that rely on it, consider replacing them with alternative packages that do not have known vulnerabilities.
Conclusion
The teaa-reborn30 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 uninstall this package and monitor their dependencies for vulnerabilities. Utilizing tools like Vulert can help in maintaining the security of your applications.
See every vulnerability recorded for teaa-reborn30 →
FAQ
teaa-reborn30 is an npm package associated with the tea.xyz token reward campaign, designed to generate and publish derivative packages.
The vulnerability can lead to the pollution of the npm registry and may compromise the security and integrity of applications that depend on the teaa-reborn30 package.
You should uninstall the teaa-reborn30 package immediately using 'npm uninstall teaa-reborn30' and check for any affected dependencies.
Yes, consider using other reputable npm packages that provide similar functionality without the associated risks.
You can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities in your software. You can check if your application is affected by this vulnerability using the Vulert playground at Vulert Scanner 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.
