Malicious Code Injection in dhratea Package: npm Vulnerability Overview

dhratea Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-97702: Malicious code in dhratea (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 dhratea package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate token rewards by generating and publishing derivative packages. However, it has been identified as containing malicious code that compromises its integrity and security.

Vulnerability Detail

The vulnerability in the dhratea package originates from its malicious payload, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior is intended to inflate developer reputation scores and pollute the npm registry with numerous derivative packages. The implications of this vulnerability include potential exposure of sensitive data and the risk of dependency confusion attacks, where malicious packages could be inadvertently used in projects.

How To Fix

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

npm uninstall dhratea

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 remove the dhratea package from your project by executing: npm uninstall dhratea. This will prevent the execution of any malicious code associated with the package.

Conclusion

The dhratea package poses a significant security risk due to its malicious code that alters project files and inflates developer reputation scores. It is crucial to update or remove this package to safeguard your project from potential threats.

See every vulnerability recorded for dhratea →

Share this vulnerability

FAQ

The dhratea package is an npm package associated with the tea.xyz token reward campaign, designed to generate and publish derivative packages.

The package modifies the package.json file, removes private flags, changes version numbers, and generates random package names to inflate developer reputation scores.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check if your application is affected without any signup.

Using the dhratea package can expose your project to security risks, including data leaks and dependency confusion attacks due to the presence of malicious code.

To prevent similar vulnerabilities, regularly audit your dependencies, utilize tools like Vulert for monitoring, and avoid using unverified packages.

How To Fix

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

npm uninstall dhratea

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