Malicious Code Injection in tealount: A Threat to npm Users
Summary
MAL-2025-98399: Malicious code in tealount (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 package 'tealount' is part of the tea.xyz token reward campaign that has recently infiltrated the npm ecosystem. It is designed to facilitate token rewards through the automatic generation and publication of derivative packages. These packages often contain scripts that manipulate package metadata and inflate developer reputation scores, posing a significant risk to the integrity of the npm registry.
Vulnerability Detail
The vulnerability in 'tealount' stems from its malicious payload, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior leads to the continuous republishing of variants, effectively polluting the npm registry. The origin of this issue is linked to a campaign aimed at exploiting npm for token rewards, which can result in compromised developer environments and potential security risks for users relying on these packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall tealountIf 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 'tealount' package and monitor your project for any dependencies that may have inadvertently included it. Regularly audit your package-lock.json file to identify and remove any malicious packages.
Conclusion
The 'tealount' package poses a significant risk due to its malicious code that alters package metadata and floods the npm registry. It is essential to remove this package and monitor your dependencies to maintain the security of your projects. Utilizing tools like Vulert can help you stay informed about vulnerabilities in your open-source software.
See every vulnerability recorded for tealount →
FAQ
'tealount' is an npm package associated with a token reward campaign that generates and publishes derivative packages to inflate developer reputation scores.
The vulnerability can lead to the modification of your package.json file, potentially compromising your project's integrity and security.
You should uninstall 'tealount' immediately using 'npm uninstall tealount' and check for any other affected packages.
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.
