Malicious Code Injection in tealoveness60 Package: npm Vulnerability Overview
Summary
MAL-2025-168790: Malicious code in tealoveness60 (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 tealoveness60 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 through automated publishing of derivative packages with randomized names. The functionality of tealoveness60 is compromised due to its malicious intent, posing a significant risk to developers and users relying on npm for package management.
Vulnerability Detail
The vulnerability in the tealoveness60 package originates from its design to include autopublish scripts that modify the package.json file. This modification removes private flags, alters version numbers, and generates random package names, leading to the continuous republishing of these variants. This behavior not only pollutes the npm registry but also compromises the integrity of the packages, potentially allowing for further exploitation and misuse.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall tealoveness60If 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 tealoveness60 package and look for alternative packages that provide similar functionality without the associated risks. Additionally, regularly monitor your package-lock.json file for any unauthorized changes.
Conclusion
The tealoveness60 package poses a significant threat due to its malicious code designed to manipulate package management processes. It is crucial for developers to be aware of such vulnerabilities and take immediate action to secure their projects. Regular monitoring and using tools like Vulert can help maintain the integrity of your software.
See every vulnerability recorded for tealoveness60 →
FAQ
Tealoveness60 is an npm package that is part of a malicious campaign aimed at inflating developer reputation scores through automated publishing.
The vulnerability can lead to unauthorized modifications in your package.json file, potentially compromising your project's integrity and security.
You should uninstall the package immediately using 'npm uninstall tealoveness60' and check for any dependencies that may be affected.
Yes, Vulert can monitor and alert you in real-time for open-source vulnerabilities in your software using just the package-lock.json file.
You can use the Vulert playground at Vulert Scanner to check if your application is affected without requiring any signup.
