Malicious Code Injection in tealove-nanami48: npm Package Vulnerability

tealove-nanami48 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-168478: Malicious code in tealove-nanami48 (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 tealove-nanami48 package 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 manipulate developer reputation scores by automatically generating and publishing derivative packages with randomized names. The primary functionality of tealove-nanami48 is to serve as a token reward mechanism, but its malicious nature compromises the integrity of the npm registry.

Vulnerability Detail

The vulnerability in tealove-nanami48 stems from its malicious code that modifies the package.json file to remove private flags and change 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 affects the reputation of developers but also poses a risk of dependency confusion and potential exploitation of other packages relying on this ecosystem.

How To Fix

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

npm uninstall tealove-nanami48

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, you can avoid using the tealove-nanami48 package and replace it with a trusted alternative that provides similar functionality without the associated risks. Always validate the source and integrity of packages before including them in your project.

Conclusion

The tealove-nanami48 package presents a significant risk due to its malicious code that alters package metadata and floods the npm registry with harmful derivatives. It is crucial to remove this package from your project and monitor your dependencies for any vulnerabilities. Utilizing tools like Vulert can help maintain the security of your application.

See every vulnerability recorded for tealove-nanami48 →

Share this vulnerability

FAQ

Tealove-nanami48 is an npm package associated with the tea.xyz token reward campaign, which has been identified as malicious due to its ability to manipulate package metadata and publish harmful derivatives.

The vulnerability can lead to dependency confusion, reputation damage for developers, and potential exploitation of your application if it relies on compromised packages.

You should uninstall the tealove-nanami48 package immediately using 'npm uninstall tealove-nanami48' and check your project for any other potentially compromised packages.

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

Yes, consider using other reputable packages that provide similar functionality without the associated risks. Always verify the source and community feedback before integrating new packages.

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

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