Malicious Code Detected in tealove-nanami28: A Threat to npm Ecosystem

tealove-nanami28 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-168457: Malicious code in tealove-nanami28 (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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The package tealove-nanami28 is part of the tea.xyz token reward campaign that has infiltrated the npm ecosystem. This package is designed to generate and publish derivative packages with randomized names, aimed at inflating developer reputation scores for token rewards. Its functionality is compromised due to the presence of malicious scripts that manipulate package metadata.

Vulnerability Detail

The vulnerability in tealove-nanami28 originates from its inclusion in a campaign that floods the npm registry with malicious packages. The malicious payload modifies the package.json file by removing private flags, altering version numbers, and generating random package names. This behavior leads to the pollution of the npm registry and can potentially harm developers by affecting their reputation and the integrity of their projects.

How To Fix

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

npm uninstall tealove-nanami28

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-nanami28 package and replace it with a trusted alternative. Always verify the integrity and source of packages before including them in your project.

Conclusion

The tealove-nanami28 package poses a significant threat to the npm ecosystem due to its malicious behavior. It is crucial for developers to be vigilant and remove any affected packages while utilizing tools like Vulert to monitor their projects for vulnerabilities.

See every vulnerability recorded for tealove-nanami28 →

Share this vulnerability

FAQ

tealove-nanami28 is an npm package that is part of a malicious campaign to inflate developer reputation scores through the creation of derivative packages.

The vulnerability can lead to the pollution of the npm registry, potentially harming your project's integrity and affecting your developer reputation.

You should uninstall the package immediately using 'npm uninstall tealove-nanami28' and check for any other affected packages.

You can use tools like Vulert, which monitors your package-lock.json file to alert you in real-time for open-source vulnerabilities.

Yes, you can use the Vulert playground at Vulert Scanner to check for vulnerabilities in your application without any signup.

How To Fix

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

npm uninstall tealove-nanami28

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