Malicious Code Injection in tealoveness58 Package - npm Vulnerability

tealoveness58 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-168787: Malicious code in tealoveness58 (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 tealoveness58 package is part of the tea.xyz token reward campaign that has been flooding the npm ecosystem. It is designed to manipulate the npm registry by generating and publishing derivative packages with randomized names. This package is particularly concerning due to its ability to modify package metadata, which can lead to reputation inflation for developers involved in the tea protocol.

Vulnerability Detail

The vulnerability in the tealoveness58 package stems from its malicious code that modifies the package.json file to remove private flags and changes version numbers. It generates random Indonesian-themed package names and continuously republishes variants, polluting the npm registry. This behavior can lead to significant security risks, including the potential for dependency confusion and the spread of malicious software through the npm ecosystem.

How To Fix

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

npm uninstall tealoveness58

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 measure, you can avoid using the tealoveness58 package and any of its derivatives. Additionally, consider using npm audit to identify and address vulnerabilities in your project's dependencies.

Conclusion

The tealoveness58 package presents a significant security risk due to its malicious code that alters package metadata and floods the npm registry. Immediate action is required to remove this package and monitor for any potential vulnerabilities in your project. Utilizing tools like Vulert can help maintain the security of your dependencies.

See every vulnerability recorded for tealoveness58 →

Share this vulnerability

FAQ

Tealoveness58 is an npm package associated with the tea.xyz token reward campaign, which has been identified as malicious due to its behavior of modifying package metadata and flooding the npm registry.

The vulnerability can lead to dependency confusion, allowing malicious code to be executed in your project, potentially compromising security and integrity.

You should immediately remove the tealoveness58 package from your project and check for any other affected packages. Use npm audit to identify vulnerabilities.

Yes, you can use tools like Vulert, which monitors your package-lock.json for open-source vulnerabilities in real-time. You can check your application against known vulnerabilities using the Vulert playground.

Regularly audit your dependencies using npm audit, keep your packages updated, and monitor for vulnerabilities using tools like Vulert.

How To Fix

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

npm uninstall tealoveness58

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