Malicious Code Injection in tealoveness50 Package - npm Vulnerability
Summary
MAL-2025-168779: Malicious code in tealoveness50 (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 tealoveness50 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 inflate developer reputation scores by automatically generating and publishing derivative packages with randomized names. The functionality of tealoveness50 is compromised due to its malicious intent, which poses a significant risk to developers and users relying on npm packages.
Vulnerability Detail
The vulnerability in the tealoveness50 package arises from its inclusion in a malicious campaign that modifies the package.json file to remove private flags and alters version numbers. It generates random package names, primarily themed around Indonesian culture, and continuously republishes these variants to pollute the npm registry. This behavior can lead to a loss of trust in the npm ecosystem, potential data leaks, and exploitation of users who unknowingly install these compromised packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall tealoveness50If 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, avoid using the tealoveness50 package and monitor your project for any dependencies that may inadvertently include it. Regularly audit your package-lock.json file to ensure no malicious packages are present.
Conclusion
The tealoveness50 package poses a significant risk due to its malicious code designed to manipulate the npm registry. Developers should take immediate action to remove this package and monitor their projects for any vulnerabilities. Utilizing tools like Vulert can aid in maintaining the security of your applications.
See every vulnerability recorded for tealoveness50 →
FAQ
Tealoveness50 is an npm package that is part of a malicious campaign aimed at inflating developer reputation scores through the automatic generation of derivative packages.
The vulnerability can lead to the introduction of malicious code into your project, potentially compromising your application's integrity and security.
You should uninstall the package immediately using 'npm uninstall tealoveness50' and check your project for any dependencies that may rely on it.
You can use tools like Vulert, which monitors your package-lock.json file for open-source vulnerabilities in real-time. You can check your application for vulnerabilities using the Vulert playground without any signup.
Currently, there is no patched version of the tealoveness50 package available. It is recommended to remove the package from your project.
