Malicious Code Injection in tealoveness72 Package: A Threat to npm Users
Summary
MAL-2025-168803: Malicious code in tealoveness72 (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 tealoveness72 package is part of a broader campaign associated with the tea.xyz token reward system, which has been flooding the npm ecosystem. This package is designed to automate the generation and publication of derivative packages, often with randomized names, to inflate developer reputation scores in exchange for tea protocol token rewards. Its functionality, while seemingly innocuous, conceals a malicious intent that can compromise the integrity of the npm registry.
Vulnerability Detail
The vulnerability in the tealoveness72 package stems from its malicious payload, which 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, effectively polluting the npm registry. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which employs autopublish scripts to automate the malicious activities. The ramifications include potential security risks for developers who inadvertently use these compromised packages, as well as a degradation of trust in the npm ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall tealoveness72If 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 tealoveness72 package altogether and look for alternative packages that provide similar functionality without the associated risks. Regularly monitor your dependencies for any updates or vulnerabilities.
Conclusion
The tealoveness72 package poses a significant threat to npm users due to its malicious code injection capabilities. It is crucial to remove this package from your projects and monitor your dependencies for vulnerabilities. Utilizing tools like Vulert can help maintain the security of your applications.
See every vulnerability recorded for tealoveness72 →
FAQ
The tealoveness72 package is part of a malicious campaign that aims to inflate developer reputation scores in exchange for token rewards, flooding the npm registry with compromised packages.
The vulnerability can lead to the introduction of malicious code into your project, potentially compromising its security and integrity.
You should uninstall the tealoveness72 package immediately using 'npm uninstall tealoveness72' and check your project for any other affected packages.
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 against known vulnerabilities using the Vulert playground without any signup.
Yes, consider looking for other npm packages that provide similar functionality but do not have the associated risks of malicious behavior.
