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

tealove-nanami35 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-168465: Malicious code in tealove-nanami35 (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-nanami35 is part of the tea.xyz token reward campaign, which has been known to flood the npm ecosystem with malicious packages. These packages are designed to inflate developer reputation scores through automated scripts that publish numerous derivative packages with randomized names. This behavior not only clutters the npm registry but also poses a risk to developers who may unknowingly use these compromised packages.

Vulnerability Detail

The vulnerability in tealove-nanami35 originates from its inclusion in a malicious campaign that modifies the package.json file to remove private flags and alters version numbers. It generates random package names, often themed around Indonesian culture, and continuously republishes these variants to pollute the npm registry. This can lead to developers inadvertently using compromised packages, which may contain harmful code or lead to security breaches in their applications.

How To Fix

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

npm uninstall tealove-nanami35

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-nanami35 package and look for alternative packages that provide similar functionality without the associated risks. Additionally, consider using tools like Vulert to monitor your dependencies for vulnerabilities.

Conclusion

The tealove-nanami35 package poses a significant risk due to its malicious code designed to manipulate the npm registry. It is essential for developers to be vigilant and remove any affected packages from their projects. Utilizing tools like Vulert can help in monitoring for such vulnerabilities in real-time.

See every vulnerability recorded for tealove-nanami35 →

Share this vulnerability

FAQ

Tealove-nanami35 is an npm package that is part of a malicious campaign aimed at inflating developer reputation scores through automated publishing of compromised packages.

The vulnerability can lead to the inclusion of malicious code in your application, potentially compromising its security and functionality.

You should uninstall the package immediately using 'npm uninstall tealove-nanami35' and check your application for any potential security issues.

You can use Vulert, which monitors your package-lock.json for vulnerabilities in real-time. You can also check if your application is affected by this vulnerability using the Vulert playground without any signup.

Yes, consider looking for other npm packages that provide similar functionality without the risks associated with tealove-nanami35.

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

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