Malicious Code Injection in tealoveness23: A Threat to npm Ecosystem

tealoveness23 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-168749: Malicious code in tealoveness23 (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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The package tealoveness23 is part of the tea.xyz token reward campaign that has infiltrated the npm ecosystem. It is designed to manipulate developer reputation scores by automatically generating and publishing derivative packages with randomized names. This package can significantly affect the integrity of the npm registry by flooding it with malicious variants.

Vulnerability Detail

The vulnerability in tealoveness23 originates from its malicious payload, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior not only compromises the security of the npm registry but also leads to the proliferation of potentially harmful packages that can mislead developers and users alike. The autopublish scripts included in the package are specifically designed to automate this malicious activity, making it a significant threat to the ecosystem.

How To Fix

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

npm uninstall tealoveness23

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 manually remove the tealoveness23 package from your project by executing the following command in your terminal: npm uninstall tealoveness23. Additionally, consider using tools like Vulert to monitor your project for vulnerabilities in real-time.

Conclusion

The tealoveness23 package poses a significant threat to the npm ecosystem due to its malicious code designed to manipulate package publishing. It is crucial for developers to be vigilant, remove any affected packages, and utilize monitoring tools like Vulert to safeguard their projects against such vulnerabilities.

See every vulnerability recorded for tealoveness23 →

Share this vulnerability

FAQ

Tealoveness23 is an npm package associated with the tea.xyz token reward campaign, known for its malicious behavior of flooding the npm registry with derivative packages.

The vulnerability can lead to the introduction of malicious packages into your project, compromising its security and integrity.

You should uninstall the package immediately and monitor your project for any other vulnerabilities.

Yes, tools like Vulert can help monitor your project for open-source vulnerabilities in real-time without requiring code access.

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 tealoveness23

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