Malicious Code Injection in tealove-nanami24: npm Package Vulnerability

tealove-nanami24 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-168453: Malicious code in tealove-nanami24 (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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The tealove-nanami24 package is part of a broader campaign associated with the tea.xyz token reward initiative, which has been known to flood the npm registry with malicious packages. These packages are designed to manipulate developer reputation scores by automatically generating and publishing derivative packages with randomized names. This behavior not only affects the integrity of the npm ecosystem but also poses significant risks to developers and users who may unknowingly incorporate these packages into their projects.

Vulnerability Detail

The vulnerability in tealove-nanami24 stems from its malicious code that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This is executed through autopublish scripts that continuously republish variants, leading to pollution of the npm registry. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which incentivizes such malicious behavior. The ramifications include potential security risks for applications using these packages, as they may inadvertently introduce vulnerabilities or unstable dependencies.

How To Fix

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

npm uninstall tealove-nanami24

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 measure, avoid using the tealove-nanami24 package and consider using alternative packages that provide similar functionality without the associated risks. Regularly audit your dependencies to ensure no malicious packages are included.

Conclusion

The tealove-nanami24 package poses a significant security risk due to its malicious code designed to manipulate npm registry integrity. It is crucial for developers to remove this package from their projects and monitor their dependencies for similar vulnerabilities. Utilizing tools like Vulert can help maintain the security of your applications.

See every vulnerability recorded for tealove-nanami24 →

Share this vulnerability

FAQ

tealove-nanami24 is an npm package that is part of a malicious campaign aimed at inflating developer reputation scores through the automatic generation of derivative packages.

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

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

You can use tools like Vulert, which monitors your package-lock.json file for open-source vulnerabilities in real-time. You can check your application for vulnerabilities using the Vulert playground without any signup.

Yes, consider using other reputable packages that offer similar functionality without the associated risks of malicious behavior.

How To Fix

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

npm uninstall tealove-nanami24

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