Malicious Code Injection in tealove-nice27: A Threat to npm Ecosystem

tealove-nice27 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-168505: Malicious code in tealove-nice27 (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 Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

tealove-nice27 is an npm package that is part of the tea.xyz token reward campaign. It is designed to facilitate the automatic generation and publication of derivative packages. This package, like many others in the campaign, is intended to inflate developer reputation scores for rewards associated with the tea protocol. However, it has been identified as containing malicious code that compromises the integrity of the npm registry.

Vulnerability Detail

The vulnerability in tealove-nice27 originates from its malicious payload, which modifies the package.json file to remove private flags and alters version numbers. It generates random package names, often themed around Indonesian culture, and continuously republishes these variants to pollute the npm registry. This behavior not only affects the reputation of legitimate 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-nice27

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 remove the tealove-nice27 package from your project by executing: npm uninstall tealove-nice27. This will prevent any potential malicious activity associated with this package until a secure version is released.

Conclusion

The tealove-nice27 package poses a significant risk due to its malicious code that alters package metadata and publishes harmful variants. It is essential to take immediate action by uninstalling the package and monitoring for updates. Utilizing tools like Vulert can help maintain the security of your dependencies.

See every vulnerability recorded for tealove-nice27 →

Share this vulnerability

FAQ

tealove-nice27 is an npm package involved in a token reward campaign that has been identified to contain malicious code.

The malicious code modifies your package.json, removes private flags, and publishes random packages, which can lead to dependency confusion and reputation damage.

You should uninstall the package immediately and monitor for any updates or patches that may be released.

Yes, you can use Vulert, which monitors your package-lock.json for vulnerabilities in real-time without requiring code access or installation.

You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.

How To Fix

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

npm uninstall tealove-nice27

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