Malicious Code Injection in dark_hoverfly_z3n: A Threat to npm Ecosystem

dark_hoverfly_z3n Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-93915: Malicious code in dark_hoverfly_z3n (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

dark_hoverfly_z3n is an npm package that is part of the tea.xyz token reward campaign. This package is designed to interact with the npm registry, and its primary functionality revolves around generating and publishing derivative packages. However, it has been identified as a malicious package that can compromise the integrity of the npm ecosystem by introducing harmful scripts.

Vulnerability Detail

The vulnerability in dark_hoverfly_z3n originates from its association with the tea.xyz token reward campaign, which has been known to flood the npm registry with malicious packages. The malicious payload modifies the package.json file by removing private flags, altering version numbers, and generating random package names. This behavior not only inflates developer reputation scores but also pollutes the npm registry with potentially harmful packages, posing a risk to developers and users relying on legitimate packages.

How To Fix

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

npm uninstall dark_hoverfly_z3n

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 measure, you can avoid using the dark_hoverfly_z3n package and look for alternative packages that provide similar functionality without the associated risks. Additionally, you can use tools like Vulert to monitor your project for vulnerabilities. For example, you can check if your application is affected by this vulnerability using the Vulert playground at https://vulert.com/scanner without any signup.

Conclusion

The dark_hoverfly_z3n package poses a significant threat to the npm ecosystem due to its malicious code that modifies package files and inflates developer reputation scores. It is essential to remove this package from your projects and monitor for vulnerabilities using tools like Vulert to ensure the security of your applications.

See every vulnerability recorded for dark_hoverfly_z3n →

Share this vulnerability

FAQ

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

The vulnerability can compromise the integrity of your project by introducing malicious code that modifies package files and inflates reputation scores, potentially leading to further security risks.

You should uninstall the dark_hoverfly_z3n package immediately using the command npm uninstall dark_hoverfly_z3n and look for secure alternatives.

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

There is no patch available for dark_hoverfly_z3n due to its malicious nature. The best course of action is to remove the package entirely.

How To Fix

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

npm uninstall dark_hoverfly_z3n

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