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

tealove-nice6 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-168532: Malicious code in tealove-nice6 (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

tealove-nice6 is an npm package that is part of the tea.xyz token reward campaign. This package is designed to facilitate token rewards by generating and publishing derivative packages. It is characterized by its use of autopublish scripts that automate the creation of numerous variants of the package, often with randomized names. However, this functionality has been exploited to introduce malicious code that compromises the integrity of the npm registry.

Vulnerability Detail

The vulnerability in tealove-nice6 originates from its malicious payload, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior leads to the continuous republishing of variants, which clutters the npm registry and can inflate developer reputation scores fraudulently. The ramifications include potential security risks for users who inadvertently install these compromised packages, as they may contain harmful code.

How To Fix

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

npm uninstall tealove-nice6

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-nice6 package until a secure version is released. Additionally, consider using alternative packages that do not exhibit malicious behavior.

Conclusion

The tealove-nice6 package poses a significant security risk due to its malicious code that alters package metadata and floods the npm registry. Users are advised to update or remove the package and utilize monitoring tools like Vulert to safeguard their applications from similar vulnerabilities.

See every vulnerability recorded for tealove-nice6 →

Share this vulnerability

FAQ

tealove-nice6 is an npm package involved in the tea.xyz token reward campaign, designed to automate the generation and publication of derivative packages.

The vulnerability can lead to the installation of malicious code, which may compromise your application's security and integrity.

Immediately update the package to the latest version or remove it from your project to prevent potential security risks.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time using just your package-lock.json file. Visit Vulert Scanner to check if your application is affected.

Regularly update your dependencies, use trusted packages, and monitor your application with tools like Vulert to stay informed about potential vulnerabilities.

How To Fix

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

npm uninstall tealove-nice6

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