Malicious Code Injection in tealoveness9: npm Package Vulnerability
Summary
MAL-2025-168808: Malicious code in tealoveness9 (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 tealoveness9 package is part of the tea.xyz token reward campaign, which has been known to flood the npm ecosystem with malicious packages. These packages are designed to manipulate developer reputation scores by automatically generating and publishing derivative packages with randomized names. The primary functionality of tealoveness9 is to participate in this token reward scheme, but it has been compromised to include harmful scripts that can affect the integrity of the npm registry.
Vulnerability Detail
The vulnerability in the tealoveness9 package originates 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 behavior leads to the continuous republishing of variants, which pollutes the npm registry and can potentially compromise other packages and applications that rely on npm. The malicious payload is executed through scripts such as auto.js and autopublish.js, which are designed to automate the exploitation process.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall tealoveness9If 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 prevent the installation of the tealoveness9 package by using the following command to uninstall it if it is already installed: npm uninstall tealoveness9. Additionally, consider using a tool like Vulert to monitor your package-lock.json for vulnerabilities in real-time.
Conclusion
The tealoveness9 package poses a significant risk due to its malicious code designed to manipulate npm registry integrity. It is crucial to remove this package and monitor your dependencies for vulnerabilities. Utilizing tools like Vulert can help maintain the security of your applications.
See every vulnerability recorded for tealoveness9 →
FAQ
Tealoveness9 is an npm package that is part of a malicious campaign aimed at manipulating developer reputation scores through the automatic generation and publication of derivative packages.
The vulnerability can lead to the pollution of the npm registry, potentially compromising other packages and applications that depend on npm, and can also affect the integrity of your project's dependencies.
You should uninstall the tealoveness9 package immediately and monitor your project for any other potentially malicious packages.
You can use Vulert, which allows you to monitor your package-lock.json for open-source 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.
