Malicious Code Injection in tealove-boy8: A Threat to npm Users

tealove-boy8 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-168162: Malicious code in tealove-boy8 (npm). Affected versions are not published. No fix is published. How to fix ↓

Free scan

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.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The package tealove-boy8 is part of a series of npm packages associated with the tea.xyz token reward campaign. These packages are designed to inflate developer reputation scores by automatically generating and publishing derivative packages with randomized names. This behavior not only clutters the npm registry but also poses a significant risk to users who may unknowingly install these malicious packages.

Vulnerability Detail

The vulnerability in tealove-boy8 originates from its malicious code that modifies the package.json file to remove private flags and alters version numbers. It generates random package names, often themed around Indonesian culture, and continuously republishes these variants to pollute the npm registry. This can lead to compromised systems, as users may inadvertently install these harmful packages, exposing their applications to security risks.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall tealove-boy8

If 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, you can avoid using the tealove-boy8 package and any other packages associated with the tea.xyz token reward campaign. Regularly audit your project's dependencies to identify and remove any potentially harmful packages.

Conclusion

The tealove-boy8 package poses a significant risk to npm users due to its malicious code designed to manipulate package metadata and flood the npm registry. It is essential to remove this package and regularly audit your dependencies to maintain the security of your projects.

See every vulnerability recorded for tealove-boy8 →

Share this vulnerability

FAQ

tealove-boy8 is an npm package that is part of a malicious campaign aimed at inflating developer reputation scores through the automatic generation of derivative packages.

You can use tools like Vulert to monitor your project for open-source vulnerabilities. By analyzing your package-lock.json file, Vulert can alert you in real-time about any vulnerabilities, including those related to tealove-boy8.

If you have installed tealove-boy8, you should uninstall it immediately using the command: npm uninstall tealove-boy8, and review your project's dependencies for any other suspicious packages.

No, there are no patches available for tealove-boy8 as it is a malicious package. The best course of action is to remove it from your project.

To prevent similar vulnerabilities, regularly audit your dependencies, keep them updated, and use tools like Vulert to monitor for vulnerabilities in real-time.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall tealove-boy8

If 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 →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback