Malicious Code Injection in tealoveness63: npm Package Vulnerability
Summary
MAL-2025-168793: Malicious code in tealoveness63 (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 tealoveness63 is part of the tea.xyz token reward campaign, which has been known to flood the npm ecosystem with malicious packages. This package is designed to manipulate npm's package registry by generating and publishing derivative packages with randomized names, ultimately aimed at inflating developer reputation scores for token rewards. Its functionality is compromised due to the presence of autopublish scripts that automate the creation of these malicious variants.
Vulnerability Detail
The vulnerability in tealoveness63 originates from its malicious code that modifies the package.json file to remove private flags and change version numbers. This allows the package to generate random Indonesian-themed names and continuously republish variants, polluting the npm registry. The ramifications include potential security risks for developers who unknowingly install these packages, as they may inadvertently contribute to the malicious ecosystem and face reputational damage.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall tealoveness63If 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 tealoveness63 package and any other packages associated with the tea.xyz token reward campaign. Regularly audit your dependencies to ensure that no malicious packages are included.
Conclusion
The tealoveness63 package poses a significant security risk due to its malicious code designed to manipulate the npm registry. It is crucial for developers to be vigilant and remove any instances of this package from their projects. Utilizing tools like Vulert can help in identifying vulnerabilities and ensuring the integrity of your software.
See every vulnerability recorded for tealoveness63 →
FAQ
Tealoveness63 is an npm package that is part of a malicious campaign aimed at inflating developer reputation scores through the creation of derivative packages.
The vulnerability can lead to the installation of malicious packages that may compromise your project's security and integrity.
You can use tools like Vulert to monitor your package-lock.json for vulnerabilities. Visit Vulert Scanner to check your application without any signup.
You should uninstall the package immediately using 'npm uninstall tealoveness63' and check for any other related malicious packages.
Yes, Vulert provides real-time monitoring and alerts for open-source vulnerabilities using just your package-lock.json.
