Malicious Code Injection in tealove-boy22: npm Package Vulnerability
Summary
MAL-2025-168128: Malicious code in tealove-boy22 (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-boy22 package is part of the tea.xyz token reward campaign that has infiltrated the npm ecosystem. This package is designed to facilitate automatic publishing of derivative packages, which are generated with randomized names to inflate developer reputation scores for tea protocol token rewards. The presence of malicious scripts within this package poses a significant risk to users and the integrity of the npm registry.
Vulnerability Detail
The vulnerability in the tealove-boy22 package originates from its inclusion in a malicious campaign that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This leads to the continuous republishing of variants, which pollutes the npm registry and can compromise the security of applications relying on these packages. The malicious payload is designed to exploit the npm ecosystem, making it critical for developers to be aware of its implications.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall tealove-boy22If 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-boy22 package and replace it with a trusted alternative. Always verify the integrity and reputation of packages before including them in your project.
Conclusion
The tealove-boy22 package poses a significant security risk due to its malicious code designed to exploit the npm ecosystem. It is crucial for developers to remove this package and monitor their dependencies for vulnerabilities. Utilizing tools like Vulert can help maintain the security of your applications.
See every vulnerability recorded for tealove-boy22 →
FAQ
The tealove-boy22 package is part of a malicious campaign that aims to inflate developer reputation scores by flooding the npm registry with derivative packages.
The vulnerability can lead to the inclusion of malicious code in your application, potentially compromising its security and integrity.
You should uninstall the tealove-boy22 package immediately and review your project's dependencies for any other potentially malicious packages.
You can use tools like Vulert, which monitors and alerts for open-source vulnerabilities in your software using just package-lock.json. You can check your application for vulnerabilities without any signup at the Vulert playground.
Yes, always look for well-maintained and widely used packages in the npm registry that serve the same purpose as tealove-boy22.
