Malicious Code Injection in tealoveness73: A Threat to npm Package Integrity

tealoveness73 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-168804: Malicious code in tealoveness73 (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 tealoveness73 is part of the tea.xyz token reward campaign that has infiltrated the npm ecosystem. It is designed to facilitate the automatic generation and publication of derivative packages, often with randomized names. This behavior is intended to inflate developer reputation scores for rewards associated with the tea protocol. However, this package is compromised, posing significant risks to users and the integrity of the npm registry.

Vulnerability Detail

The vulnerability in tealoveness73 originates from its malicious payload, which modifies the package.json file to remove private flags and alters version numbers. It generates random package names, primarily themed around Indonesian culture, and continuously republishes these variants to pollute the npm registry. This behavior can lead to a loss of trust in the npm ecosystem, potential data breaches, and the inadvertent installation of malicious software by developers unaware of the compromised package.

How To Fix

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

npm uninstall tealoveness73

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 tealoveness73 package and look for alternative packages that provide similar functionality without the associated risks. Additionally, consider using tools like Vulert to monitor your project for vulnerabilities. You can check if your application is affected by this vulnerability using the Vulert playground at https://vulert.com/scanner without needing to sign up.

Conclusion

The tealoveness73 package poses a significant threat due to its malicious code that compromises the integrity of the npm registry. Users are advised to uninstall the package and monitor their projects for vulnerabilities using tools like Vulert. Staying informed and proactive is essential to maintaining the security of your software.

See every vulnerability recorded for tealoveness73 →

Share this vulnerability

FAQ

Tealoveness73 is an npm package that is part of a token reward campaign, designed to generate and publish derivative packages automatically.

The package modifies package.json files, removes private flags, changes version numbers, and generates random package names to pollute the npm registry.

You can use the Vulert playground at Vulert Scanner to check if your application is affected by the tealoveness73 vulnerability.

You should uninstall the package immediately using 'npm uninstall tealoveness73' and look for alternative packages.

Currently, there is no patched version available. It is recommended to remove the package and monitor for any updates.

How To Fix

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

npm uninstall tealoveness73

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