Malicious Code Injection in tealoveness64: A Threat to npm Packages
Summary
MAL-2025-168794: Malicious code in tealoveness64 (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 package tealoveness64 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 inflate developer reputation scores by automatically generating and publishing derivative packages with randomized names. This behavior not only compromises the integrity of the npm registry but also poses significant risks to developers who may unknowingly use these compromised packages.
Vulnerability Detail
The vulnerability in tealoveness64 originates from its malicious payload, which modifies the package.json file to remove private flags and alters version numbers. It generates random Indonesian-themed package names and continuously republishes variants, effectively polluting the npm registry. This can lead to a loss of trust in the npm ecosystem, as developers may inadvertently install compromised packages, exposing their applications to further vulnerabilities.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall tealoveness64If 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, avoid using the tealoveness64 package and consider using alternative packages that provide similar functionality without the associated risks. Always verify the integrity of packages before installation.
Conclusion
The tealoveness64 package poses a significant threat due to its malicious behavior aimed at manipulating the npm registry. It is crucial for developers to be vigilant, regularly audit their dependencies, and utilize tools like Vulert to monitor for vulnerabilities. By taking proactive measures, developers can protect their applications from potential risks associated with compromised packages.
See every vulnerability recorded for tealoveness64 →
FAQ
Tealoveness64 is an npm package that has been identified as part of a malicious campaign aimed at inflating developer reputation scores through the publication of compromised packages.
The vulnerability can lead to the installation of malicious code, which may compromise your application's security and integrity, potentially exposing sensitive data or allowing unauthorized access.
If you have installed tealoveness64, you should immediately uninstall it using 'npm uninstall tealoveness64' and review your project's dependencies for any other potentially compromised packages.
You can use tools like Vulert, which monitors your package-lock.json file to alert you in real-time for open-source vulnerabilities. You can also check your application for vulnerabilities using the Vulert playground at Vulert Scanner without any signup.
Yes, there are many alternative packages available on npm that provide similar functionality. Always ensure to choose well-maintained and trusted packages.
