Malicious Code Injection in tealoveness15 Package: npm Vulnerability Overview

tealoveness15 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-168740: Malicious code in tealoveness15 (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 Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The tealoveness15 package is part of the tea.xyz token reward campaign that has infiltrated the npm ecosystem. This package is designed to facilitate the automatic generation and publishing of derivative packages, which are often used to inflate developer reputation scores in exchange for tea protocol token rewards. The package's functionality includes creating and publishing random Indonesian-themed package names, which can lead to pollution of the npm registry.

Vulnerability Detail

The vulnerability in the tealoveness15 package originates from its malicious code that modifies the package.json file to remove private flags and change version numbers. This allows the package to generate random names and continuously republish variants, thereby polluting the npm registry. The ramifications include potential security risks for developers who unknowingly use these packages, as they may inadvertently introduce malicious code into their applications.

How To Fix

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

npm uninstall tealoveness15

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 tealoveness15 package and any packages that depend on it. Regularly audit your package-lock.json file to identify and remove any potentially malicious packages.

Conclusion

The tealoveness15 package poses a significant risk due to its malicious code that modifies package.json files and repopulates the npm registry with harmful variants. It is crucial for developers to be vigilant and remove this package from their projects to maintain application security.

See every vulnerability recorded for tealoveness15 →

Share this vulnerability

FAQ

Tealoveness15 is an npm package involved in the tea.xyz token reward campaign, designed to generate and publish derivative packages.

The vulnerability can lead to the introduction of malicious code into your application, potentially compromising its security.

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

You should uninstall the package immediately and audit your project for any other potentially malicious packages.

Currently, there is no patched version available. It is recommended to remove the package from your project.

How To Fix

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

npm uninstall tealoveness15

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