Malicious Code Injection in deep_dragonfly-apptea: npm Package Vulnerability

deep_dragonfly-apptea Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-101257: Malicious code in deep_dragonfly-apptea (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 Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The deep_dragonfly-apptea package is part of the tea.xyz token reward campaign that has infiltrated the npm ecosystem. This package is designed to facilitate the distribution of token rewards through various scripts that automate the publication of derivative packages. However, it has been identified as containing malicious code that compromises the integrity of the npm registry.

Vulnerability Detail

The vulnerability originates from the deep_dragonfly-apptea package, which includes scripts that automatically modify the package.json file to remove private flags, alter version numbers, and generate random package names. This behavior leads to the proliferation of derivative packages that can inflate developer reputation scores fraudulently. The malicious payload continuously republishes these variants, polluting the npm registry and potentially affecting other developers and users relying on the integrity of the ecosystem.

How To Fix

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

npm uninstall deep_dragonfly-apptea

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 prevent the installation of this package by using npm's package-lock.json to monitor dependencies. If you are using Vulert, you can check if your application is affected by this vulnerability without any signup by visiting https://vulert.com/scanner.

Conclusion

The deep_dragonfly-apptea package poses a significant risk due to its malicious code that alters package metadata and floods the npm registry with derivative packages. It is crucial for developers to remove this package and monitor their dependencies for vulnerabilities to maintain the integrity of their applications.

See every vulnerability recorded for deep_dragonfly-apptea →

Share this vulnerability

FAQ

deep_dragonfly-apptea is an npm package associated with the tea.xyz token reward campaign, designed to automate the publication of derivative packages.

The vulnerability can lead to the proliferation of malicious packages that may compromise your application's integrity and security.

You should remove the deep_dragonfly-apptea package from your project and check for any updates or patches.

Yes, Vulert can monitor your package-lock.json file for vulnerabilities in real-time, alerting you to any issues without requiring code access.

Yes, you can use the Vulert playground at Vulert Scanner to check for vulnerabilities in your application without any signup.

How To Fix

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

npm uninstall deep_dragonfly-apptea

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