Malicious Code Vulnerability in tealove-boy13 Package
Summary
MAL-2025-168118: Malicious code in tealove-boy13 (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-boy13 package is part of a broader campaign associated with the tea.xyz token reward system, which has been flooding the npm ecosystem. This package is designed to facilitate token rewards through the generation and publication of derivative packages. It typically includes scripts that automate the publishing process, which can lead to reputation inflation for developers involved in the tea protocol.
Vulnerability Detail
The vulnerability in the tealove-boy13 package stems from its malicious code, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior allows the package to continuously republish variants, polluting the npm registry and potentially compromising the integrity of other packages. The malicious payload is part of a larger scheme to exploit the npm ecosystem for token rewards, making it a significant threat to developers and users alike.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall tealove-boy13If 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-boy13 package altogether and look for alternative packages that provide similar functionality without the associated risks. Additionally, consider using tools like Vulert to monitor your project for vulnerabilities.
Conclusion
The tealove-boy13 package poses a significant risk due to its malicious code that alters package metadata and repopulates the npm registry with potentially harmful variants. It is essential to remove this package from your projects and monitor for any vulnerabilities using tools like Vulert.
See every vulnerability recorded for tealove-boy13 →
FAQ
The tealove-boy13 package is part of a campaign that generates and publishes derivative packages to exploit the npm ecosystem for token rewards.
The vulnerability can lead to the pollution of the npm registry and compromise the integrity of your project by introducing malicious code.
You should uninstall the tealove-boy13 package immediately and check your package-lock.json for any references to it.
Yes, you can use Vulert to monitor your project for open-source vulnerabilities in real-time without requiring code access or installation.
You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without signing up.
