Malicious Code Injection in tealoveness68 Package - npm Vulnerability
Summary
MAL-2025-168798: Malicious code in tealoveness68 (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 tealoveness68 package is part of a broader campaign associated with the tea.xyz token reward system, which has been known to flood the npm registry 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 tealoveness68 is to serve as a tool within this ecosystem, but its malicious behavior poses significant risks to developers and users alike.
Vulnerability Detail
The vulnerability in the tealoveness68 package stems from its inclusion in a malicious campaign that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior leads to the continuous republishing of variants, which pollutes the npm registry and can compromise the integrity of projects that depend on this package. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which exploits npm's publishing system for malicious purposes.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall tealoveness68If 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
Currently, there are no specific workarounds to mitigate the risks posed by the tealoveness68 package other than removing it from your project. Ensure that you regularly audit your dependencies to avoid similar vulnerabilities.
Conclusion
The tealoveness68 package poses a significant security risk due to its malicious code designed to manipulate npm's publishing system. It is crucial for developers to remove this package from their projects and stay vigilant about their dependencies to maintain the integrity of their applications.
See every vulnerability recorded for tealoveness68 →
FAQ
Tealoveness68 is an npm package associated with a malicious campaign that aims to manipulate 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 and exposing it to further risks.
You should uninstall the tealoveness68 package immediately to mitigate any potential risks associated with its malicious behavior.
As of now, there is no patched version available. The best course of action is to remove the package from your project.
You can use tools like Vulert, which monitors and alerts in real-time for open-source vulnerabilities in your software. You can check if your application is affected by this vulnerability using the Vulert playground without any signup.
