Malicious Code Injection in tealoveness11: A Threat to npm Users
Summary
MAL-2025-168736: Malicious code in tealoveness11 (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 package tealoveness11 is part of a broader campaign associated with the tea.xyz token reward initiative, which has been known to flood the npm ecosystem with malicious packages. These packages are designed to manipulate npm's publishing system, often containing scripts that automatically generate and publish derivative packages with randomized names. This behavior not only inflates developer reputation scores but also poses significant risks to the integrity of the npm registry.
Vulnerability Detail
The vulnerability in tealoveness11 stems from its inclusion in a malicious package campaign that modifies the package.json file to remove private flags and alters version numbers. It generates random package names, often themed around Indonesian culture, and continuously republishes these variants. This behavior can lead to the pollution of the npm registry, making it difficult for developers to trust the packages they use and potentially exposing their applications to further vulnerabilities.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall tealoveness11If 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 tealoveness11 package and monitor your project for any dependencies that may indirectly include it. Regularly check your package-lock.json file for any unexpected changes or additions.
Conclusion
The tealoveness11 package poses a significant threat to npm users due to its malicious behavior aimed at manipulating the npm registry. It is crucial to remove this package from your projects and utilize tools like Vulert to monitor for vulnerabilities in your dependencies. Staying informed and proactive can help maintain the security of your applications.
See every vulnerability recorded for tealoveness11 →
FAQ
Tealoveness11 is an npm package that is part of a malicious campaign aimed at manipulating the npm registry.
The vulnerability can lead to the pollution of the npm registry, making it difficult to trust other packages and potentially exposing your application to further security risks.
You should uninstall the package immediately using 'npm uninstall tealoveness11' and review your dependencies for any other malicious packages.
You can use tools like Vulert, which monitors your package-lock.json for open-source vulnerabilities in real-time. You can also check your application against vulnerabilities using the Vulert playground without any signup.
There are no patches available for tealoveness11 as it is a malicious package. The best course of action is to remove it from your project.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
