Malicious Code Injection in tealove-dana34: A Threat to npm Packages

tealove-dana34 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-168241: Malicious code in tealove-dana34 (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 Your last release was probably never penetration tested 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 tealove-dana34 is part of a broader campaign associated with the tea.xyz token reward system, which has infiltrated the npm ecosystem. This package is designed to manipulate npm's package management system, primarily targeting developers looking to enhance their reputation through token rewards. Its functionality includes generating and publishing derivative packages with randomized names, which can lead to significant pollution of the npm registry.

Vulnerability Detail

The vulnerability in tealove-dana34 stems from its malicious code that modifies the package.json file by removing private flags and altering version numbers. This code is part of a larger scheme to automatically generate and publish numerous derivative packages, thereby inflating developer reputation scores fraudulently. The malicious payload can lead to the proliferation of unwanted packages in the npm registry, potentially causing confusion and security risks for developers and users alike.

How To Fix

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

npm uninstall tealove-dana34

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 tealove-dana34 package by using npm's package-lock.json to monitor your dependencies. You can also utilize tools like Vulert to check for vulnerabilities in your application without needing to install any software. For example, you can visit the Vulert playground at https://vulert.com/scanner to see if your application is affected by this vulnerability.

Conclusion

The tealove-dana34 package poses a significant threat to the npm ecosystem due to its malicious code designed to manipulate package management. It is essential for developers to be vigilant and regularly check their dependencies for vulnerabilities. By uninstalling affected packages and utilizing tools like Vulert, developers can safeguard their projects against such threats.

See every vulnerability recorded for tealove-dana34 →

Share this vulnerability

FAQ

Tealove-dana34 is an npm package involved in a malicious campaign aimed at manipulating developer reputation scores through the tea.xyz token reward system.

The vulnerability can lead to the proliferation of unwanted and potentially harmful packages in your project, which may compromise security and cause confusion.

You should uninstall the package immediately using 'npm uninstall tealove-dana34' and check your project for any other affected dependencies.

You can use tools like Vulert, which allows you to monitor and alert for open-source vulnerabilities in real-time using just your package-lock.json.

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by vulnerabilities without needing to sign up.

How To Fix

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

npm uninstall tealove-dana34

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