Malicious Code Injection in teanager Package: npm Vulnerability Overview
Summary
MAL-2025-168809: Malicious code in teanager (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 teanager package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate various functionalities, but it has been compromised to include malicious scripts that can manipulate package metadata and inflate developer reputation scores. The vulnerability arises from the package's ability to modify its own package.json file, which can lead to significant issues in the npm registry.
Vulnerability Detail
The vulnerability in the teanager package stems from its inclusion in a malicious 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 pollutes the npm registry but also poses a risk to developers who may unknowingly install these compromised packages, leading to potential security breaches in their applications.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall teanagerIf 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 teanager package altogether or restrict its usage in your project until a secure version is released. Additionally, consider using tools like Vulert to monitor your package-lock.json for vulnerabilities.
Conclusion
The teanager package has been identified as containing malicious code that can compromise the integrity of npm projects. It is crucial for developers to stay informed about such vulnerabilities and take proactive measures to secure their applications by updating packages and utilizing monitoring tools like Vulert.
See every vulnerability recorded for teanager →
FAQ
The teanager package is an npm package associated with the tea.xyz token reward campaign, which has been compromised to include malicious code.
The malicious code can modify your package.json file, inflate developer reputation scores, and potentially lead to the installation of compromised packages.
If you have installed teanager, you should update it to the latest version or remove it from your project to mitigate the risk.
You can use tools like 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 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.
