Malicious Code Injection in linear_hoverfly_z3n: A Threat to npm Packages

linear_hoverfly_z3n Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-87879: Malicious code in linear_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 linear_hoverfly_z3n package is part of the npm ecosystem, which is widely used for JavaScript development. This package, like many others, is intended to facilitate certain functionalities within applications. However, it has been identified as part of a malicious campaign that exploits npm's package management system, leading to significant security concerns for developers and users alike.

Vulnerability Detail

The vulnerability in linear_hoverfly_z3n stems from its association with a malicious campaign that floods the npm registry with derivative packages. The malicious code modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior not only compromises the integrity of the affected package but also pollutes the npm registry, potentially affecting other packages and developers relying on npm for their projects.

How To Fix

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

npm uninstall linear_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 workaround, you can avoid using the linear_hoverfly_z3n package and look for alternative packages that provide similar functionality without the associated risks. Always verify the source and reputation of packages before including them in your project.

Conclusion

The linear_hoverfly_z3n package poses a significant security risk due to its malicious code injection. It is essential for developers to be vigilant about the packages they use and to regularly monitor for vulnerabilities. By uninstalling the affected package and utilizing tools like Vulert, developers can protect their applications from potential threats.

See every vulnerability recorded for linear_hoverfly_z3n →

Share this vulnerability

FAQ

linear_hoverfly_z3n is an npm package used in JavaScript development, but it has been identified as part of a malicious campaign.

The vulnerability can lead to the injection of malicious code, compromising the integrity of your application and potentially affecting other packages.

You should uninstall the linear_hoverfly_z3n package immediately and look for secure alternatives.

You can use tools like Vulert, which monitors your package-lock.json for open-source vulnerabilities in real-time without requiring code access.

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.

How To Fix

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

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