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

tealove-nanami17 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-168445: Malicious code in tealove-nanami17 (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-nanami17 is part of a broader campaign associated with the tea.xyz token reward initiative, which has been known to flood the npm ecosystem with malicious packages. These packages are designed to manipulate npm's publishing system, often containing scripts that automatically generate and publish derivative packages. The primary functionality of tealove-nanami17 is to act as a token reward mechanism, but its vulnerability exposes users to significant risks, including the potential for reputation score inflation and registry pollution.

Vulnerability Detail

The vulnerability in tealove-nanami17 originates from its design to include autopublish scripts that modify the package.json file. These scripts remove private flags, alter version numbers, and create random package names, leading to the continuous republishing of variants. This not only compromises the integrity of the npm registry but also poses risks to developers who may unknowingly use these malicious packages, potentially leading to security breaches and loss of trust in the ecosystem.

How To Fix

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

npm uninstall tealove-nanami17

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 tealove-nanami17 and any other packages associated with the tea.xyz token reward campaign. Regularly audit your package dependencies using tools like npm audit to identify and mitigate risks from malicious packages.

Conclusion

The tealove-nanami17 package poses a significant risk due to its malicious code designed to manipulate npm's publishing system. It is crucial for developers to remain vigilant, regularly audit their dependencies, and utilize tools like Vulert to monitor for vulnerabilities. By taking proactive measures, you can help safeguard your projects from potential threats.

See every vulnerability recorded for tealove-nanami17 →

Share this vulnerability

FAQ

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

The vulnerability can lead to the modification of your package.json file, removal of private flags, and the introduction of random package names, which can compromise your project's integrity and security.

You should uninstall the package immediately using npm uninstall tealove-nanami17 and check your project for any other potentially malicious dependencies.

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

Yes, tools like npm audit and Vulert can help identify and alert you to malicious packages in your dependencies.

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

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