Malicious Code Injection in tealove-nameka20 Package

tealove-nameka20 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-168402: Malicious code in tealove-nameka20 (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 Your last release was probably never penetration tested 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-nameka20 package is part of the tea.xyz token reward campaign, which has been known to flood the npm ecosystem with numerous packages. These packages often include scripts that automatically generate and publish derivative packages with randomized names. The primary function of these packages is to inflate developer reputation scores for token rewards, but they also pose significant risks due to their malicious behavior.

Vulnerability Detail

The vulnerability in the tealove-nameka20 package stems from the inclusion of autopublish scripts that modify the package.json file. This modification removes private flags, alters version numbers, and generates random package names, leading to the continuous republishing of variants. This behavior pollutes the npm registry and can compromise the integrity of applications relying on this package. The malicious code is designed to exploit the npm ecosystem for personal gain, making it a significant threat to developers and users alike.

How To Fix

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

npm uninstall tealove-nameka20

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, avoid using the tealove-nameka20 package and consider using alternative packages that provide similar functionality without the associated risks. Additionally, regularly monitor your package-lock.json file for any signs of malicious packages using tools like Vulert, which can alert you to vulnerabilities in real-time.

Conclusion

The tealove-nameka20 package poses a significant risk due to its malicious code that modifies package.json files and repopulates the npm registry with harmful variants. It is crucial for developers to remove this package and monitor their projects for vulnerabilities to maintain application integrity.

See every vulnerability recorded for tealove-nameka20 →

Share this vulnerability

FAQ

Tealove-nameka20 is an npm package associated with the tea.xyz token reward campaign, designed to inflate developer reputation scores.

The vulnerability can lead to the modification of your package.json file, potentially compromising your application's integrity and security.

You should uninstall the tealove-nameka20 package immediately and monitor your project for any other malicious packages.

You can use tools like Vulert, which allows you to monitor your package-lock.json file for vulnerabilities without requiring code access or installation.

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without signing up.

How To Fix

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

npm uninstall tealove-nameka20

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