Malicious Code Injection in teaa-reborn17 Package - npm Vulnerability
Summary
MAL-2025-166714: Malicious code in teaa-reborn17 (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-reborn17 package is part of the tea.xyz token reward campaign, which has been known to flood the npm ecosystem with various packages. These packages are designed to automate the generation and publication of derivative packages, often with randomized names, to inflate developer reputation scores for token rewards. This behavior raises significant concerns regarding the integrity and security of the npm registry.
Vulnerability Detail
The vulnerability in the teaa-reborn17 package stems from its inclusion in a malicious campaign that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This malicious payload continuously republishes variants, polluting the npm registry and potentially compromising the security of applications that depend on this package. The origin of this vulnerability is linked to the automated scripts (auto.js, autopublish.js, etc.) that are part of the package's design, aimed at exploiting the npm ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall teaa-reborn17If 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 measure, you can avoid using the teaa-reborn17 package and any other packages associated with the tea.xyz token reward campaign. Regularly audit your project's dependencies to ensure that no malicious packages are included.
Conclusion
The teaa-reborn17 package poses a significant security risk due to its malicious code designed to manipulate the npm registry. It is essential to remove this package from your projects and monitor your dependencies for similar vulnerabilities. Utilizing tools like Vulert can help maintain the security of your applications.
See every vulnerability recorded for teaa-reborn17 →
FAQ
The teaa-reborn17 package is part of a campaign that aims to inflate developer reputation scores through the automated publication of derivative packages on npm.
The vulnerability can lead to the inclusion of malicious code in your application, potentially compromising its security and integrity.
You should uninstall the teaa-reborn17 package immediately to prevent any potential security risks.
Yes, you can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities in your software using just package-lock.json.
You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.
