Malicious Code Injection in tealove-nice43: A Threat to npm Packages

tealove-nice43 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-168523: Malicious code in tealove-nice43 (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 Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

Background

The package 'tealove-nice43' is part of a series of npm packages associated with the tea.xyz token reward campaign. These packages are designed to manipulate the npm registry by generating and publishing numerous derivative packages with randomized names. This behavior is intended to inflate developer reputation scores for rewards associated with the tea protocol, making it a significant concern for developers relying on npm for package management.

Vulnerability Detail

The vulnerability in 'tealove-nice43' stems from its malicious code, which modifies the package.json file to remove private flags and alters version numbers. It generates random package names, primarily themed around Indonesian culture, and continuously republishes these variants to pollute the npm registry. This not only compromises the integrity of the npm ecosystem but also poses risks to developers who may unknowingly integrate these malicious packages into their projects.

How To Fix

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

npm uninstall tealove-nice43

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-nice43' package and any other packages associated with the tea.xyz campaign. Monitor your package-lock.json file for any unauthorized changes or additions, and consider using tools like Vulert to keep track of vulnerabilities in your dependencies.

Conclusion

The 'tealove-nice43' package poses a significant risk due to its malicious code that alters package metadata and floods the npm registry with unauthorized packages. It is crucial for developers to remove this package and monitor their dependencies for vulnerabilities to maintain the integrity of their projects.

See every vulnerability recorded for tealove-nice43 →

Share this vulnerability

FAQ

'tealove-nice43' is an npm package linked to a token reward campaign that aims to manipulate the npm registry.

The malicious code can compromise your project's integrity by introducing unauthorized changes and potentially harmful packages.

You should uninstall the package immediately using 'npm uninstall tealove-nice43' and review your project for any other affected packages.

You can use tools like Vulert, which monitors your package-lock.json for vulnerabilities in real-time without requiring code access or installation.

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without signing up.

Sponsored Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

How To Fix

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

npm uninstall tealove-nice43

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