Malicious Code Injection in tealove-boy5: A Threat to npm Users
Summary
MAL-2025-168158: Malicious code in tealove-boy5 (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-boy5 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 malicious behavior of tealove-boy5 includes altering the package.json file to remove private flags and changing version numbers, which can lead to significant security risks for users relying on this package.
Vulnerability Detail
The vulnerability in tealove-boy5 stems from its malicious code that modifies the package.json file, removing private flags and generating random package names. This behavior is part of a scheme to inflate developer reputation scores for token rewards, leading to the continuous republishing of variants that pollute the npm registry. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which exploits npm's publishing mechanisms to distribute malicious packages widely. The ramifications include potential exposure of sensitive information and the risk of dependency confusion attacks, where legitimate packages may be overshadowed by these malicious variants.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall tealove-boy5If 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, users can avoid using the tealove-boy5 package and consider alternative packages that provide similar functionality without the associated risks. Additionally, implementing strict dependency management practices can help mitigate the impact of such vulnerabilities.
Conclusion
The tealove-boy5 package poses a significant security risk due to its malicious code designed to manipulate npm's publishing system. Users are advised to remove this package and monitor their dependencies for vulnerabilities. Utilizing tools like Vulert can help maintain the security of your software projects.
See every vulnerability recorded for tealove-boy5 →
FAQ
Tealove-boy5 is an npm package that is part of a malicious campaign designed to inflate developer reputation scores through the automatic generation and publication of derivative packages.
The vulnerability can lead to the exposure of sensitive information and may allow malicious actors to manipulate your project's dependencies, potentially causing security breaches.
You should immediately remove the tealove-boy5 package from your project and monitor for any updates or patches that may address this vulnerability.
You can use tools like Vulert, which monitors your package-lock.json file to alert you in real-time for open-source vulnerabilities in your software. You can check your application against known vulnerabilities using the Vulert playground.
Yes, consider using other reputable packages that provide similar functionality without the associated risks of malicious behavior.
