Malicious Code Injection in tealove-boy36: A Threat to npm Ecosystem
Summary
MAL-2025-168143: Malicious code in tealove-boy36 (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-boy36 is part of a series of malicious npm packages associated with the tea.xyz token reward campaign. These packages are designed to manipulate the npm registry by generating and publishing numerous derivative packages with randomized names. This activity aims to inflate developer reputation scores for token rewards, compromising the integrity of the npm ecosystem.
Vulnerability Detail
The vulnerability in tealove-boy36 originates from its malicious payload, which modifies the package.json file by removing private flags and altering version numbers. It generates random package names, primarily themed around Indonesian culture, and continuously republishes these variants, leading to pollution of the npm registry. This not only affects the reputation of legitimate developers but also poses security risks by potentially introducing harmful code into projects that depend on these packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall tealove-boy36If 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, avoid using the tealove-boy36 package and any other packages associated with the tea.xyz token reward campaign. Regularly audit your dependencies to ensure that no malicious packages are included.
Conclusion
The tealove-boy36 package poses a significant risk to the npm ecosystem due to its malicious code injection capabilities. It is crucial for developers to remain vigilant, regularly audit their dependencies, and utilize tools like Vulert to monitor for vulnerabilities. Taking immediate action to remove affected packages is essential to maintain the security and integrity of your projects.
See every vulnerability recorded for tealove-boy36 →
FAQ
Tealove-boy36 is an npm package identified as part of a malicious campaign that aims to manipulate the npm registry.
The vulnerability can lead to the introduction of malicious code into your project, compromising its security and integrity.
You should uninstall the package immediately using 'npm uninstall tealove-boy36' and check your project for any related vulnerabilities.
You can use tools like Vulert, which monitors your package-lock.json file for open-source vulnerabilities in real-time without requiring code access or installation.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without signing up.
