Malicious Code Injection in tealove-nice48: npm Package Vulnerability

tealove-nice48 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-168528: Malicious code in tealove-nice48 (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

The package tealove-nice48 is part of the tea.xyz token reward campaign, which has been known to flood the npm registry with malicious packages. These packages are designed to inflate developer reputation scores through automated scripts that generate and publish derivative packages with randomized names. The primary functionality of tealove-nice48 is to act as a token reward mechanism, but its malicious nature compromises the integrity of the npm ecosystem.

Vulnerability Detail

The vulnerability in tealove-nice48 originates from its inclusion in a campaign that utilizes autopublish scripts to create and publish numerous derivative packages. These scripts modify the package.json file by removing private flags, altering version numbers, and generating random package names. This behavior leads to pollution of the npm registry, potentially affecting developers who rely on the integrity of package sources. The malicious payload can also lead to unintended consequences for applications that depend on these compromised packages.

How To Fix

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

npm uninstall tealove-nice48

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 workaround, you can avoid using the tealove-nice48 package altogether. If it is already included in your project, remove it by executing the following command: npm uninstall tealove-nice48. Additionally, consider using tools like Vulert to monitor your dependencies for vulnerabilities.

Conclusion

The tealove-nice48 package poses a significant risk due to its malicious code that alters package metadata and floods the npm registry. It is crucial for developers to remove this package and monitor their dependencies for vulnerabilities using tools like Vulert. Staying informed and proactive can help maintain the security of your applications.

See every vulnerability recorded for tealove-nice48 →

Share this vulnerability

FAQ

tealove-nice48 is an npm package associated with the tea.xyz token reward campaign, which has been identified as containing malicious code.

The malicious code can modify your package.json file, remove private flags, and publish derivative packages, potentially compromising your application's integrity.

You can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.

If you have installed tealove-nice48, you should uninstall it immediately using the command: npm uninstall tealove-nice48.

Yes, Vulert provides a service that monitors your package-lock.json for open-source vulnerabilities in real-time, alerting you to any issues.

How To Fix

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

npm uninstall tealove-nice48

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