Malicious Code Injection in tealove-boy7: npm Package Vulnerability

tealove-boy7 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-168161: Malicious code in tealove-boy7 (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-boy7 is part of a broader campaign associated with the tea.xyz token reward initiative. This npm package is designed to facilitate the automatic generation and publication of derivative packages, which are often created to inflate developer reputation scores for rewards. The package's functionality revolves around manipulating package metadata and publishing behavior, making it susceptible to exploitation.

Vulnerability Detail

The vulnerability in tealove-boy7 originates from its inclusion in a malicious campaign that floods the npm registry with derivative packages. The malicious code modifies the package.json file by removing private flags, altering version numbers, and generating random package names, which can lead to the pollution of the npm registry. This behavior not only compromises the integrity of the npm ecosystem but also poses risks to developers who may unknowingly use these tainted packages, potentially leading to security breaches in their applications.

How To Fix

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

npm uninstall tealove-boy7

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 workaround, you can avoid using the tealove-boy7 package and any other packages associated with the tea.xyz campaign. Instead, look for alternative packages that provide similar functionality without the associated risks.

Conclusion

The tealove-boy7 package is a malicious npm package that poses significant risks to developers and the integrity of the npm ecosystem. It is essential to remove this package and any similar ones from your projects to safeguard against potential vulnerabilities. Regular monitoring and updating of dependencies are crucial for maintaining application security.

See every vulnerability recorded for tealove-boy7 →

Share this vulnerability

FAQ

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

The vulnerability can lead to the pollution of the npm registry and may introduce security risks if your application inadvertently uses compromised packages.

You should uninstall the package immediately using the command npm uninstall tealove-boy7 and review your dependencies for any other potentially malicious packages.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time using just your package-lock.json file. You can also check your application against known vulnerabilities using the Vulert playground.

There is no patch available for tealove-boy7 as it is a malicious package. The best course of action is to remove it from your project.

How To Fix

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

npm uninstall tealove-boy7

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