Malicious Code Injection in tealove-nanami36 Package

tealove-nanami36 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-168466: Malicious code in tealove-nanami36 (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 Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The tealove-nanami36 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 publication of derivative packages, which are often used to inflate developer reputation scores for token rewards. Its functionality is compromised by malicious scripts that manipulate package metadata.

Vulnerability Detail

The vulnerability in the tealove-nanami36 package originates from its association with a malicious campaign that floods the npm registry with derivative packages. The malicious payload modifies the package.json file by removing private flags, altering version numbers, and generating random package names. This leads to pollution of the npm registry and can potentially compromise the integrity of applications relying on this package.

How To Fix

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

npm uninstall tealove-nanami36

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-nanami36 package altogether and look for alternative packages that provide similar functionality without the associated risks.

Conclusion

The tealove-nanami36 package poses a significant risk due to its malicious code that alters package metadata and floods the npm registry. It is crucial to remove this package and monitor your applications for vulnerabilities. Utilizing tools like Vulert can help in maintaining the security of your open-source dependencies.

See every vulnerability recorded for tealove-nanami36 →

Share this vulnerability

FAQ

tealove-nanami36 is an npm package that is part of a malicious campaign to inflate developer reputation scores through automated package publishing.

The vulnerability can lead to the pollution of the npm registry, potentially compromising the integrity of your application and exposing it to further risks.

You should uninstall the tealove-nanami36 package immediately and monitor your application for any unusual behavior.

Yes, you can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities using just your package-lock.json file. You can check your application against this vulnerability using the Vulert playground.

You can use the Vulert playground at Vulert Scanner to check if your application is affected by the tealove-nanami36 vulnerability without needing to sign up.

How To Fix

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

npm uninstall tealove-nanami36

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