Malicious Code Injection in tealoveness54 Package: npm Vulnerability Overview

tealoveness54 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-168783: Malicious code in tealoveness54 (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 tealoveness54 package is part of the tea.xyz token reward campaign that has infiltrated the npm ecosystem. It is designed to facilitate token rewards through the automatic generation and publication of derivative packages. This package is characterized by its use of scripts that create numerous variants of itself, often with randomized names, to manipulate developer reputation scores.

Vulnerability Detail

The vulnerability in the tealoveness54 package stems from its malicious code that modifies the package.json file. This code removes private flags, alters version numbers, and generates random package names, leading to a pollution of the npm registry. The malicious payload is part of a broader scheme to inflate developer reputation scores for rewards, posing risks of dependency confusion and potential exploitation of affected applications.

How To Fix

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

npm uninstall tealoveness54

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 prevent the installation of the tealoveness54 package by using npm's package-lock.json to lock your dependencies. This will ensure that the vulnerable package is not installed inadvertently. Additionally, consider using tools like Vulert to monitor your project for vulnerabilities in real-time.

Conclusion

The tealoveness54 package presents a significant security risk due to its malicious code that alters package metadata and floods the npm registry. It is essential for developers to remove this package from their projects and utilize tools like Vulert to monitor for vulnerabilities effectively.

See every vulnerability recorded for tealoveness54 →

Share this vulnerability

FAQ

Tealoveness54 is an npm package associated with the tea.xyz token reward campaign, designed to generate and publish derivative packages.

The vulnerability can lead to dependency confusion, allowing malicious code to execute within your application, potentially compromising security.

You should uninstall the package immediately using 'npm uninstall tealoveness54' and check for any dependencies that may be affected.

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

Currently, there is no patched version available for tealoveness54. The best course of action is to remove the package entirely.

How To Fix

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

npm uninstall tealoveness54

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