Malicious Code Injection in tealoveness8: A Threat to npm Ecosystem
Summary
MAL-2025-168807: Malicious code in tealoveness8 (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 tealoveness8 is part of the tea.xyz token reward campaign, which has been associated with a surge of malicious packages on npm. These packages are designed to manipulate the npm registry by generating and publishing numerous derivative packages with random names, ultimately aiming to inflate developer reputation scores for token rewards. The functionality of tealoveness8 is compromised due to its malicious intent, making it a significant threat to developers and the integrity of the npm ecosystem.
Vulnerability Detail
The vulnerability in tealoveness8 stems from its inclusion in a campaign that floods the npm registry with malicious packages. The malicious code modifies the package.json file to remove private flags, alters version numbers, and generates random package names, leading to the continuous republishing of these variants. This not only pollutes the npm registry but also poses a risk of dependency confusion and potential exploitation by other malicious actors.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall tealoveness8If 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 workaround, you can monitor your package-lock.json file for any unauthorized changes or additions. Regularly audit your npm packages using npm audit to identify and address vulnerabilities promptly.
Conclusion
The tealoveness8 package poses a significant threat to the npm ecosystem due to its malicious code designed to manipulate the registry. Developers are urged to remove this package and monitor their projects for any vulnerabilities. Utilizing tools like Vulert can help in maintaining the security of your applications.
See every vulnerability recorded for tealoveness8 →
FAQ
Tealoveness8 is an npm package that is part of a malicious campaign aimed at manipulating the npm registry for token rewards.
The vulnerability can lead to the pollution of your project's dependencies, making it susceptible to further attacks and dependency confusion.
You should uninstall the package immediately and monitor your project for any unauthorized changes.
Yes, you can use Vulert to monitor your application for vulnerabilities by analyzing your package-lock.json file. Visit Vulert Scanner for more information.
Regularly audit your dependencies, use tools like Vulert for real-time monitoring, and avoid installing unverified packages from npm.
