Malicious Code Injection in tealove-boy19: A Threat to npm Users
Summary
MAL-2025-168124: Malicious code in tealove-boy19 (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 tealove-boy19 is part of a series of npm packages associated with the tea.xyz token reward campaign. These packages are designed to manipulate npm's ecosystem by automatically generating and publishing derivative packages with randomized names. This behavior is intended to inflate developer reputation scores for rewards associated with the tea protocol, posing a significant risk to the integrity of the npm registry.
Vulnerability Detail
The vulnerability in tealove-boy19 stems from its malicious code that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This leads to the continuous republishing of variants that pollute the npm registry, potentially compromising the security and reliability of applications that depend on these packages. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which exploits npm's publishing mechanisms.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall tealove-boy19If 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 tealove-boy19 package and monitor your project for any dependencies that might indirectly include it. Regularly audit your package-lock.json file to ensure no malicious packages are included.
Conclusion
The tealove-boy19 package poses a significant threat due to its malicious code designed to manipulate the npm ecosystem. 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, you can protect your applications from potential risks associated with malicious packages.
See every vulnerability recorded for tealove-boy19 →
FAQ
Tealove-boy19 is an npm package that is part of a malicious campaign aimed at manipulating the npm registry for token rewards.
The vulnerability can lead to the inclusion of malicious code in your application, potentially compromising its security and integrity.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without needing to sign up.
You should uninstall the package immediately and review your dependencies for any other potentially malicious packages.
Yes, Vulert provides a service that uses package-lock.json to monitor for vulnerabilities in your software, allowing you to stay informed about potential risks.
