Malicious Code Injection in tealove-boy4: npm Package Vulnerability
Summary
MAL-2025-168147: Malicious code in tealove-boy4 (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-boy4 is part of a broader campaign associated with the tea.xyz token reward system. It is designed to manipulate the npm registry by automatically generating and publishing derivative packages. This behavior is intended to inflate developer reputation scores for rewards related to the tea protocol. The package's functionality includes creating random package names and modifying existing package configurations.
Vulnerability Detail
The vulnerability in tealove-boy4 stems from its malicious code that alters the package.json file by removing private flags and changing version numbers. It generates random package names, often themed around Indonesian culture, and continuously republishes these variants to clutter the npm registry. This not only compromises the integrity of the npm ecosystem but also poses risks to developers who may unknowingly use these tainted packages, potentially leading to security breaches and loss of trust in the package management system.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall tealove-boy4If 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 measure, you can avoid using the tealove-boy4 package and any other packages associated with the tea.xyz token reward campaign. Monitor your package-lock.json file for any unauthorized changes and consider using tools like Vulert to keep track of vulnerabilities in your dependencies.
Conclusion
The tealove-boy4 package presents a significant security risk due to its malicious code that alters package configurations and floods the npm registry. It is essential to remove this package from your projects and utilize monitoring tools like Vulert to safeguard against future vulnerabilities.
See every vulnerability recorded for tealove-boy4 →
FAQ
Tealove-boy4 is an npm package associated with the tea.xyz token reward campaign, designed to manipulate the npm registry.
The vulnerability can lead to the introduction of malicious code into your project, compromising its security and integrity.
You should uninstall the package immediately using 'npm uninstall tealove-boy4' and review your project for any potential impacts.
You can use tools like Vulert, which monitors your package-lock.json file for vulnerabilities in real-time without requiring installation.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.
