Malicious Code Injection in tealove-boy9 Package: npm Vulnerability Summary
Summary
MAL-2025-168163: Malicious code in tealove-boy9 (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
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
Background
The tealove-boy9 package is part of the tea.xyz token reward campaign, which has been known to flood the npm registry with various packages. These packages are designed to inflate developer reputation scores through the automatic generation and publication of derivative packages. The functionality of tealove-boy9 is compromised due to its malicious intent, which includes modifying package metadata and republishing variants to pollute the npm registry.
Vulnerability Detail
The vulnerability in the tealove-boy9 package stems from its malicious code that modifies the package.json file by removing private flags and changing version numbers. It generates random package names, often themed around Indonesian culture, and continuously republishes these variants. This behavior not only compromises the integrity of the npm registry but also poses a risk to developers who may unknowingly use these tainted packages, leading to potential security breaches and loss of reputation.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall tealove-boy9If 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, avoid using the tealove-boy9 package and monitor your package-lock.json file for any unauthorized changes. Regularly audit your dependencies to ensure no malicious packages are present.
Conclusion
The tealove-boy9 package poses a significant risk due to its malicious code that alters package metadata and repopulates the npm registry with compromised versions. It is crucial to remove this package from your project and monitor your dependencies regularly to maintain security.
See every vulnerability recorded for tealove-boy9 →
FAQ
Tealove-boy9 is an npm package that is part of a campaign to inflate developer reputation scores through the automatic generation of derivative packages.
The vulnerability can lead to unauthorized modifications in your package.json file and the introduction of malicious code, which can compromise your project's security.
You should uninstall the tealove-boy9 package immediately using the command: npm uninstall tealove-boy9.
Yes, you can use tools like Vulert, which monitors your package-lock.json file for open-source vulnerabilities in real-time without requiring code access.
You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
