Malicious Code Injection in tealove-nice49: A Threat to npm Users

tealove-nice49 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-168529: Malicious code in tealove-nice49 (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-nice49 is part of the tea.xyz token reward campaign that has infiltrated the npm ecosystem. It is designed to generate and publish derivative packages with randomized names, aiming to inflate developer reputation scores for token rewards. This malicious behavior poses a significant risk to developers and users relying on npm packages.

Vulnerability Detail

The vulnerability in tealove-nice49 originates from its malicious code, which modifies the package.json file to remove private flags and alters version numbers. It generates random Indonesian-themed package names and continuously republishes variants, polluting the npm registry. This can lead to the installation of compromised packages, potentially exposing users to security risks and undermining the integrity of the npm ecosystem.

How To Fix

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

npm uninstall tealove-nice49

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 the tealove-nice49 package and monitor your project for any dependencies that may have been affected by this malicious package. Regularly audit your npm packages using 'npm audit' to identify and address vulnerabilities.

Conclusion

The tealove-nice49 package poses a significant threat to npm users due to its malicious code designed to manipulate package metadata and publish compromised variants. It is crucial to remove this package and monitor your dependencies to maintain the security of your projects.

See every vulnerability recorded for tealove-nice49 →

Share this vulnerability

FAQ

Tealove-nice49 is an npm package that has been identified as malicious, part of a campaign to inflate developer reputation scores through the publication of compromised packages.

The vulnerability can lead to the installation of malicious code, which may compromise your project's security and integrity by introducing unwanted behavior or exposing sensitive data.

You should immediately uninstall the package using 'npm uninstall tealove-nice49' and check for any other affected packages in your project.

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 vulnerabilities using the Vulert playground at Vulert Scanner.

Regularly audit your npm packages, keep them updated, and utilize monitoring tools like Vulert to stay informed about vulnerabilities in your dependencies.

How To Fix

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

npm uninstall tealove-nice49

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