Malicious Code Injection in teaa-reborn36: A Threat to npm Ecosystem
Summary
MAL-2025-166733: Malicious code in teaa-reborn36 (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-reborn36 is an npm package that is part of the tea.xyz token reward campaign. This package is designed to interact with the npm registry, allowing developers to publish and manage their packages. However, it has been identified as malicious, containing scripts that manipulate package metadata and inflate developer reputation scores through automated publishing.
Vulnerability Detail
The vulnerability in teaa-reborn36 stems from its inclusion in a campaign that floods the npm registry with derivative packages. The malicious code modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior not only compromises the integrity of the npm ecosystem but also poses risks to developers who may unknowingly install these malicious packages, leading to potential security breaches and loss of trust in the npm registry.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall teaa-reborn36If 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, avoid using the teaa-reborn36 package and monitor your project for any dependencies that may inadvertently include it. You can also use tools like Vulert to monitor your package-lock.json for vulnerabilities.
Conclusion
The teaa-reborn36 package poses a significant threat to the npm ecosystem due to its malicious code that manipulates package metadata and floods the registry with unauthorized packages. It is crucial for developers to remove this package and monitor their projects for vulnerabilities to maintain the integrity of their applications.
See every vulnerability recorded for teaa-reborn36 →
FAQ
teaa-reborn36 is an npm package associated with the tea.xyz token reward campaign, which has been identified as malicious.
The malicious code can modify your package.json file, remove private flags, and publish unauthorized packages, compromising your project's integrity.
You should uninstall the package immediately using 'npm uninstall teaa-reborn36' and check for any other affected packages.
You can use Vulert, which monitors your package-lock.json for vulnerabilities in real-time without requiring code access or installation.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without signing up.
