Malicious Code Injection in tealove-dana20 Package

tealove-dana20 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-168226: Malicious code in tealove-dana20 (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 tealove-dana20 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 automated scripts that publish derivative packages with randomized names. The presence of such malicious code poses a significant risk to developers and users relying on npm packages.

Vulnerability Detail

The vulnerability in the tealove-dana20 package stems from its malicious payload that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior leads to the continuous republishing of variants, polluting the npm registry and potentially compromising the integrity of the software supply chain. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which employs autopublish scripts to manipulate package listings.

How To Fix

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

npm uninstall tealove-dana20

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 tealove-dana20 package and replace it with a trusted alternative that provides similar functionality. Always verify the integrity and reputation of packages before including them in your project.

Conclusion

The tealove-dana20 package contains malicious code that poses a significant risk to developers and users in the npm ecosystem. It is crucial to remove this package and monitor your dependencies for vulnerabilities to maintain the integrity of your projects.

See every vulnerability recorded for tealove-dana20 →

Share this vulnerability

FAQ

The tealove-dana20 package is part of a malicious campaign that aims to inflate developer reputation scores through the automated publication 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 risks.

You should uninstall the package immediately using 'npm uninstall tealove-dana20' and review your dependencies for any other potentially malicious packages.

You can use tools like Vulert, which monitors your package-lock.json file to alert you in real-time for open-source vulnerabilities. You can check your application using the Vulert playground without any signup.

Yes, you should look for well-reviewed and actively maintained packages that provide similar functionality without the associated risks.

How To Fix

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

npm uninstall tealove-dana20

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