Malicious Code Injection in tealove-boy32 Package - npm Vulnerability
Summary
MAL-2025-168139: Malicious code in tealove-boy32 (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 tealove-boy32 package is part of the tea.xyz token reward campaign, which has been associated with a series of malicious npm packages. These packages are designed to inflate developer reputation scores by automatically generating and publishing derivative packages with randomized names. This behavior can lead to significant pollution of the npm registry and compromise the integrity of the ecosystem.
Vulnerability Detail
The vulnerability in the tealove-boy32 package stems from its malicious payload that modifies the package.json file to remove private flags and alter version numbers. It generates random package names, primarily themed around Indonesian culture, and continuously republishes these variants. This not only inflates the developer's reputation but also clutters the npm registry, making it difficult for legitimate packages to be found and used. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which exploits the npm ecosystem for malicious purposes.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall tealove-boy32If 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-boy32 package and any other packages associated with the tea.xyz campaign. Additionally, consider using tools like Vulert to monitor your package-lock.json for vulnerabilities and receive real-time alerts.
Conclusion
The tealove-boy32 package poses a significant risk due to its malicious behavior aimed at manipulating the npm ecosystem. It is crucial for developers to be aware of such vulnerabilities and take proactive measures to secure their projects by removing affected packages and utilizing monitoring tools like Vulert.
See every vulnerability recorded for tealove-boy32 →
FAQ
Tealove-boy32 is an npm package that is part of a malicious campaign aimed at inflating developer reputation scores through the automatic generation of derivative packages.
The vulnerability can lead to the pollution of the npm registry, making it harder to find legitimate packages and potentially compromising the security of your project.
You should remove the tealove-boy32 package from your project and monitor for any updates or patches that may be released.
You can use tools like Vulert, which requires only your package-lock.json file to monitor and alert you in real-time for open-source vulnerabilities.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.
