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

tealove-nanami14 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-168442: Malicious code in tealove-nanami14 (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-nanami14 is part of the tea.xyz token reward campaign, which has been associated with a surge of malicious npm packages. These packages are designed to inflate developer reputation scores through automated publishing scripts. The vulnerability in tealove-nanami14 allows for the modification of package metadata, leading to potential abuse and pollution of the npm registry.

Vulnerability Detail

The vulnerability stems from the presence of malicious code within the tealove-nanami14 package. This code is designed to alter the package.json file by removing private flags, changing version numbers, and generating random package names. The malicious payload continuously republishes these variants, which can lead to a significant pollution of the npm registry and compromise the integrity of other packages. The origin of this issue is linked to the tea.xyz token reward campaign, which employs these tactics to manipulate developer reputation scores.

How To Fix

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

npm uninstall tealove-nanami14

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-nanami14 package and monitor your project for any dependencies that may indirectly include it. Regularly check your package-lock.json file for any signs of this package and remove it if found.

Conclusion

The tealove-nanami14 package poses a significant risk due to its malicious code that alters package metadata and republishing behavior. It is crucial to remove this package from your project and monitor for any related vulnerabilities to maintain the integrity of your software.

See every vulnerability recorded for tealove-nanami14 →

Share this vulnerability

FAQ

Tealove-nanami14 is an npm package associated with the tea.xyz token reward campaign, which has been identified as containing malicious code.

The malicious code modifies your package.json file, potentially leading to the publication of unauthorized packages and pollution of the npm registry.

You should uninstall the package immediately using npm uninstall tealove-nanami14 and check your project for any other affected dependencies.

Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time using your package-lock.json. You can check your application for vulnerabilities without signup at the Vulert playground.

Regularly audit your dependencies, use tools like Vulert for monitoring, and stay informed about known vulnerabilities in the packages you use.

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-nanami14

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