Malicious Code Injection in tealoveness44 Package: npm Vulnerability Overview
Summary
MAL-2025-168772: Malicious code in tealoveness44 (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 tealoveness44 package is part of the tea.xyz token reward campaign that has infiltrated the npm ecosystem. It is designed to facilitate the generation and publication of derivative packages, often with randomized names, to inflate developer reputation scores for token rewards. This package is particularly concerning due to its ability to modify critical files within a project, leading to potential security risks.
Vulnerability Detail
The vulnerability in the tealoveness44 package stems from its malicious payload, which modifies the package.json file by removing private flags and altering version numbers. It generates random package names, primarily themed around Indonesian culture, and continuously republishes these variants to pollute the npm registry. This behavior not only compromises the integrity of the npm ecosystem but also poses risks to developers who may unknowingly use these compromised packages in their projects.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall tealoveness44If 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, avoid using the tealoveness44 package and monitor your dependencies regularly. You can utilize tools like Vulert to keep track of vulnerabilities in your project. To check if your application is affected by this vulnerability, you can use the Vulert playground at https://vulert.com/scanner without any signup.
Conclusion
The tealoveness44 package presents a significant security risk due to its malicious code that alters project files and publishes unauthorized packages. Developers are advised to remove this package and utilize tools like Vulert for ongoing monitoring of vulnerabilities in their projects.
See every vulnerability recorded for tealoveness44 →
FAQ
Tealoveness44 is an npm package associated with the tea.xyz token reward campaign, which aims to inflate developer reputation scores through the automatic generation of derivative packages.
The vulnerability can lead to unauthorized modifications in your package.json file, potentially exposing your project to security risks and affecting its integrity.
The best way to fix the vulnerability is to uninstall the tealoveness44 package from your project and ensure that your package.json and package-lock.json files are clean of any references to it.
Yes, you can use Vulert, which monitors and alerts you in real-time for open-source vulnerabilities using just your package-lock.json file.
You can check if your application is affected by this vulnerability by using the Vulert playground at Vulert Scanner without needing to sign up.
