Malicious Code Vulnerability in tealove-dana37 Package

tealove-dana37 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-168244: Malicious code in tealove-dana37 (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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The tealove-dana37 package is part of the tea.xyz token reward campaign that has infiltrated the npm ecosystem. This package is designed to facilitate the automatic generation and publication of derivative packages, which are often used to inflate developer reputation scores in exchange for tea protocol token rewards. The package's functionality revolves around creating and publishing these variants, which can lead to significant pollution of the npm registry.

Vulnerability Detail

The vulnerability in the tealove-dana37 package stems from its malicious payload that modifies the package.json file. It removes private flags, alters version numbers, and generates random package names, primarily themed around Indonesian culture. This behavior not only compromises the integrity of the npm registry but also poses risks to developers who may unknowingly use these compromised packages. The origin of this vulnerability is linked to the broader tea.xyz token reward campaign, which aims to exploit npm for personal gain.

How To Fix

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

npm uninstall tealove-dana37

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-dana37 package altogether. If it is already included in your project, you can remove it using the following command: npm uninstall tealove-dana37. Additionally, consider using tools like Vulert to monitor your project for vulnerabilities in real-time.

Conclusion

The tealove-dana37 package poses a significant risk due to its malicious behavior aimed at manipulating the npm registry. It is crucial for developers to be aware of this vulnerability, take necessary actions to remove the package, and utilize tools like Vulert for ongoing monitoring of their projects.

See every vulnerability recorded for tealove-dana37 →

Share this vulnerability

FAQ

The tealove-dana37 package is part of a malicious campaign that generates and publishes derivative npm packages to inflate developer reputation scores.

This vulnerability can lead to the pollution of the npm registry and may compromise the integrity of your project if you inadvertently use affected packages.

You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.

If you have installed the tealove-dana37 package, it is recommended to uninstall it immediately and monitor your project for any further vulnerabilities.

Yes, Vulert provides a service that monitors your package-lock.json file for open-source vulnerabilities in real-time, alerting you to any issues.

How To Fix

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

npm uninstall tealove-dana37

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