Malicious Code Injection in tealove-boy24 Package - npm Vulnerability

tealove-boy24 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-168130: Malicious code in tealove-boy24 (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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The tealove-boy24 package is part of the tea.xyz token reward campaign that has infiltrated the npm ecosystem. This package is designed to facilitate token rewards by generating and publishing derivative packages. It is characterized by its use of autopublish scripts that create numerous variants of the package, aimed at inflating developer reputation scores within the tea protocol.

Vulnerability Detail

The vulnerability in the tealove-boy24 package stems from its malicious code that modifies the package.json file. This code removes private flags, alters version numbers, and generates random package names, leading to the continuous republishing of these variants. The primary risk is the pollution of the npm registry, which can compromise the integrity of the ecosystem and potentially lead to further exploitation by malicious actors.

How To Fix

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

npm uninstall tealove-boy24

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-boy24 package and any of its derivatives. Additionally, consider using npm audit to identify and address vulnerabilities in your project's dependencies.

Conclusion

The tealove-boy24 package poses a significant risk due to its malicious code that alters package configurations and floods the npm registry. It is essential to remove this package and monitor for updates or patches to maintain the security of your project.

See every vulnerability recorded for tealove-boy24 →

Share this vulnerability

FAQ

Tealove-boy24 is an npm package associated with the tea.xyz token reward campaign, which aims to inflate developer reputation scores.

The vulnerability can lead to the pollution of the npm registry, which may compromise the integrity of your project's dependencies and expose it to further risks.

You can use the Vulert platform to monitor and alert for open-source vulnerabilities in your software. Visit Vulert Scanner to check your application without any signup.

If you have installed the tealove-boy24 package, it is recommended to remove it immediately and monitor your project for any unusual behavior.

Yes, tools like Vulert can help monitor your dependencies for vulnerabilities in real-time using just your package-lock.json file.

How To Fix

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

npm uninstall tealove-boy24

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