Malicious Code Injection in tealoveness24: A Threat to npm Packages

tealoveness24 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-168750: Malicious code in tealoveness24 (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 tealoveness24 is part of the tea.xyz token reward campaign that has infiltrated the npm ecosystem. This package is designed to engage in malicious activities, including the automatic generation and publication of derivative packages. It aims to inflate developer reputation scores for rewards associated with the tea protocol, making it a significant threat to the integrity of the npm registry.

Vulnerability Detail

The vulnerability in tealoveness24 originates from its malicious design, which includes scripts that modify the package.json file to remove private flags, alter version numbers, and generate random package names. This behavior leads to the continuous republishing of variants that pollute the npm registry, potentially compromising the security and reliability of other packages and applications that depend on npm.

How To Fix

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

npm uninstall tealoveness24

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 tealoveness24 package from your project by executing the following command: npm uninstall tealoveness24. This will prevent any malicious code from executing until a safe version is available.

Conclusion

The tealoveness24 package poses a significant risk due to its malicious code designed to manipulate the npm registry. It is crucial for developers to be vigilant, remove affected packages, and utilize monitoring tools like Vulert to safeguard their applications from potential threats.

See every vulnerability recorded for tealoveness24 →

Share this vulnerability

FAQ

Tealoveness24 is an npm package that is part of a malicious campaign aimed at inflating developer reputation scores through the automatic generation of derivative packages.

The vulnerability can lead to the pollution of the npm registry, which may compromise the security and reliability of your application by introducing malicious code through affected packages.

You should uninstall the tealoveness24 package immediately and monitor for any updates or patches that may address the vulnerability.

Yes, you can use tools like Vulert, which monitors and alerts for open-source vulnerabilities in your software by analyzing the package-lock.json file.

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

How To Fix

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

npm uninstall tealoveness24

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