Malicious Code Injection in tealove-boy29 Package - npm Vulnerability
Summary
MAL-2025-168135: Malicious code in tealove-boy29 (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-boy29 package is part of a series of npm packages associated with the tea.xyz token reward campaign. These packages are designed to automate the generation and publication of derivative packages, often with randomized names, to inflate developer reputation scores in exchange for tea protocol token rewards. The package is primarily used within the npm ecosystem, which is a popular platform for JavaScript developers to share and manage code.
Vulnerability Detail
The vulnerability in the tealove-boy29 package stems from its malicious payload, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior leads to the continuous republishing of these variants, effectively polluting the npm registry. The origin of this issue is linked to the broader trend of malicious packages flooding the npm ecosystem, aimed at exploiting developer reputation systems for token rewards. The ramifications include potential security risks for developers who unknowingly integrate these packages into their projects, as well as the degradation of the npm registry's integrity.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall tealove-boy29If 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 workaround, you can avoid using the tealove-boy29 package and instead look for alternative packages that provide similar functionality without the associated risks. Additionally, consider using tools like Vulert to monitor your project's dependencies for vulnerabilities.
Conclusion
The tealove-boy29 package presents a significant security risk due to its malicious code that modifies package metadata and floods the npm registry with derivative packages. It is crucial for developers to remove this package from their projects and utilize tools like Vulert to monitor for vulnerabilities in their dependencies.
See every vulnerability recorded for tealove-boy29 →
FAQ
The tealove-boy29 package is an npm package associated with the tea.xyz token reward campaign, designed to automate the generation and publication of derivative packages.
The vulnerability can lead to the inclusion of malicious code in your project, which may compromise security and affect the integrity of your application.
You should immediately uninstall the tealove-boy29 package using the command npm uninstall tealove-boy29 and check your project for any other affected packages.
Yes, Vulert allows you to monitor and alert for open-source vulnerabilities in your software using just the package-lock.json file. You can check your application for vulnerabilities without any signup at the Vulert playground.
To prevent similar vulnerabilities, regularly audit your dependencies, use tools like Vulert for real-time monitoring, and avoid using unverified packages from the npm registry.
