Malicious Code Injection in tealoveness62 Package: A Threat to npm Users
Summary
MAL-2025-168792: Malicious code in tealoveness62 (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 tealoveness62 package is part of a broader campaign associated with the tea.xyz token reward system, 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 tealoveness62 is to facilitate this malicious activity, posing significant risks to developers and users alike.
Vulnerability Detail
The vulnerability in the tealoveness62 package stems from its inclusion in a campaign that utilizes autopublish scripts to modify package.json files. This modification removes private flags, alters version numbers, and generates random package names, leading to the continuous republishing of variants that pollute the npm registry. The origin of this issue is linked to the tea.xyz token reward campaign, which incentivizes the creation of these malicious packages, potentially compromising the integrity of the npm ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall tealoveness62If 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 prevent the installation of the tealoveness62 package by using npm's package-lock.json file to lock your dependencies. Ensure that your project does not include this package by reviewing your package.json and removing any references to it.
Conclusion
The tealoveness62 package poses a significant threat to the npm ecosystem due to its malicious code designed to manipulate package publishing. It is essential for developers to remove this package from their projects and monitor their dependencies for vulnerabilities to maintain the integrity of their applications.
See every vulnerability recorded for tealoveness62 →
FAQ
Tealoveness62 is an npm package associated with a malicious campaign that aims to inflate developer reputation scores through the automatic generation of derivative packages.
The vulnerability can lead to the pollution of the npm registry, potentially compromising the integrity of your project's dependencies and exposing it to further security risks.
You should uninstall the package immediately using the command 'npm uninstall tealoveness62' and review your package.json file for any references to 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 without any signup at the Vulert playground.
No patches are available for tealoveness62, as it is recommended to remove the package entirely from your project.
