Malicious Code Injection in tealove-boy35: A Threat to npm Ecosystem
Summary
MAL-2025-168142: Malicious code in tealove-boy35 (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-boy35 is part of the tea.xyz token reward campaign, 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 functionality of tealove-boy35 is compromised due to its malicious intent, posing a significant risk to developers and the integrity of the npm ecosystem.
Vulnerability Detail
The vulnerability in tealove-boy35 originates from its inclusion in a campaign that utilizes autopublish scripts to create and publish numerous derivative packages. These scripts modify the package.json file to remove private flags, alter version numbers, and generate random package names, leading to pollution of the npm registry. The ramifications include potential security risks for developers who unknowingly integrate these malicious packages into their projects, as well as damage to the reputation of the npm ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall tealove-boy35If 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-boy35 package altogether and look for alternative packages that provide similar functionality without the associated risks. Always verify the integrity and reputation of packages before including them in your project.
Conclusion
The tealove-boy35 package poses a significant threat to the npm ecosystem due to its malicious code designed to manipulate package publication and developer reputation. It is crucial for developers to be vigilant, remove affected packages, and utilize tools like Vulert to monitor for vulnerabilities in their projects.
See every vulnerability recorded for tealove-boy35 →
FAQ
Tealove-boy35 is an npm package that is part of a malicious campaign aimed at inflating developer reputation scores through the publication of numerous derivative packages.
The vulnerability can lead to the inclusion of malicious code in your project, potentially compromising security and stability.
You should uninstall the package immediately using the command: npm uninstall tealove-boy35.
You can use tools like Vulert, which monitors and alerts for open-source vulnerabilities in your software by analyzing the package-lock.json file.
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.
