Malicious Code Injection in tealove-dana9 Package

tealove-dana9 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-168263: Malicious code in tealove-dana9 (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 tealove-dana9 package 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 inflate developer reputation scores through the automatic generation and publication of derivative packages with randomized names. The functionality of tealove-dana9 is compromised due to its malicious payload, which modifies critical files and repurposes the package for nefarious activities.

Vulnerability Detail

The vulnerability in the tealove-dana9 package stems from its inclusion in a campaign that utilizes autopublish scripts to generate and publish numerous derivative packages. This malicious behavior modifies the package.json file by removing private flags, altering version numbers, and creating random package names. The continuous republishing of these variants leads to pollution of the npm registry, potentially impacting developers and users who rely on the integrity of the npm ecosystem.

How To Fix

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

npm uninstall tealove-dana9

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 workaround, you can avoid using the tealove-dana9 package and replace it with a trusted alternative that provides similar functionality without the associated risks. Additionally, regularly audit your npm packages for vulnerabilities using tools like npm audit.

Conclusion

The tealove-dana9 package poses 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 monitor their dependencies for vulnerabilities to maintain the integrity of their applications.

See every vulnerability recorded for tealove-dana9 →

Share this vulnerability

FAQ

Tealove-dana9 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 pollution of the npm registry, potentially compromising the integrity of your project and exposing it to further security risks.

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

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

Regularly audit your dependencies, use trusted sources for packages, and stay informed about known vulnerabilities in the npm ecosystem.

How To Fix

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

npm uninstall tealove-dana9

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