Malicious Code Injection in tealove-dana13: npm Package Vulnerability

tealove-dana13 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-168218: Malicious code in tealove-dana13 (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 Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

Background

The package tealove-dana13 is part of the tea.xyz token reward campaign, which has been known to flood the npm ecosystem with malicious packages. These packages are designed to manipulate the npm registry by automatically generating and publishing derivative packages with randomized names, ultimately inflating developer reputation scores for token rewards. The vulnerability stems from the package's ability to modify critical files, such as package.json, leading to potential security risks for developers using this package.

Vulnerability Detail

The vulnerability in tealove-dana13 originates from its malicious design, which includes scripts that remove private flags from package.json, alter version numbers, and generate random package names. This behavior not only pollutes the npm registry but also poses a risk to developers who may unknowingly use these compromised packages. The continuous republishing of these variants can lead to a loss of trust in the npm ecosystem and can potentially expose users to further security threats.

How To Fix

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

npm uninstall tealove-dana13

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, avoid using the tealove-dana13 package and consider using alternative packages that provide similar functionality without the associated risks. Additionally, regularly monitor your package dependencies for vulnerabilities using tools like Vulert.

Conclusion

The tealove-dana13 package presents a significant security risk due to its malicious code designed to manipulate the npm registry. It is crucial for developers to remove this package from their projects and utilize monitoring tools like Vulert to stay informed about potential vulnerabilities in their dependencies.

See every vulnerability recorded for tealove-dana13 →

Share this vulnerability

FAQ

Tealove-dana13 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 modification of your package.json file, potentially exposing your project to further security risks and polluting the npm registry.

You should uninstall the package immediately using the command npm uninstall tealove-dana13 and monitor your project for any other vulnerabilities.

Yes, tools like Vulert can help monitor your dependencies for vulnerabilities in real-time. You can check your application using the Vulert playground without any signup.

Regularly audit your dependencies, use trusted packages, and employ tools like Vulert to monitor for vulnerabilities in your project.

Sponsored Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

How To Fix

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

npm uninstall tealove-dana13

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