Malicious Code Injection in numerous_hoverfly_z3n Package

numerous_hoverfly_z3n Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-106409: Malicious code in numerous_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 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 numerous_hoverfly_z3n package is part of the npm ecosystem, often utilized for various development tasks. However, it has been identified as part of a malicious campaign that exploits npm's package management system. This package, like others in the campaign, is designed to inflate developer reputation scores through the automatic generation and publication of derivative packages with randomized names.

Vulnerability Detail

The vulnerability stems from the malicious code embedded in the numerous_hoverfly_z3n package, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior is part of a broader scheme to pollute the npm registry and manipulate developer reputation scores. The potential ramifications include the introduction of insecure packages into projects, leading to further exploitation and security risks.

How To Fix

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

npm uninstall numerous_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 numerous_hoverfly_z3n package in your projects. Additionally, consider using npm audit to identify and address vulnerabilities in your dependencies.

Conclusion

The numerous_hoverfly_z3n package poses a significant security risk due to its malicious code that alters package metadata and publishes insecure variants. It is crucial for developers to remove this package and regularly audit their dependencies to maintain the security of their applications.

See every vulnerability recorded for numerous_hoverfly_z3n →

Share this vulnerability

FAQ

It is an npm package that has been identified as part of a malicious campaign to manipulate developer reputation scores.

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

Remove the numerous_hoverfly_z3n package from your project and check for any other affected packages.

It can lead to the introduction of insecure packages, potentially compromising the security and integrity of your project.

Regularly audit your dependencies using tools like npm audit and monitor for updates or vulnerabilities using services like Vulert.

How To Fix

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

npm uninstall numerous_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