Malicious Code Detected in following_hoverfly-biggestdev Package - npm Vulnerability

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-102847: Malicious code in following_hoverfly-biggestdev (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 Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

Background

The following_hoverfly-biggestdev package is part of the npm ecosystem, which is widely used for JavaScript package management. This package is suspected to be involved in a token reward campaign that has led to the proliferation of malicious packages on npm. Its primary functionality is to provide developers with tools or libraries, but it has been compromised to serve malicious purposes.

Vulnerability Detail

The vulnerability originates from the package being part of a campaign that floods npm with malicious packages. These packages contain scripts designed to automatically publish derivative packages with randomized names, which can inflate developer reputation scores for token rewards. The malicious payload modifies the package.json file to remove private flags, alters version numbers, and continuously republishes variants, leading to pollution of the npm registry. This can result in security risks for developers who unknowingly use these compromised packages.

How To Fix

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

npm uninstall following_hoverfly-biggestdev

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, avoid using the following_hoverfly-biggestdev package and look for alternative packages that provide similar functionality without the associated risks. You can also use tools like Vulert to monitor your dependencies for vulnerabilities.

Conclusion

The following_hoverfly-biggestdev package has been identified as containing malicious code that can compromise the integrity of applications using it. Developers are advised to uninstall this package and monitor their dependencies for vulnerabilities using tools like Vulert.

See every vulnerability recorded for following_hoverfly-biggestdev →

Share this vulnerability

FAQ

It is an npm package that has been compromised to include malicious code aimed at inflating developer reputation scores through automated publishing.

You can use Vulert's playground at Vulert Scanner to check if your application is affected without requiring any signup.

You should uninstall the package immediately using 'npm uninstall following_hoverfly-biggestdev' and look for alternatives.

Using this package can lead to security vulnerabilities, including the risk of your application being compromised or polluted with malicious code.

Vulert uses your package-lock.json file to monitor and alert you in real-time for open-source vulnerabilities in your software.

Sponsored Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

How To Fix

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

npm uninstall following_hoverfly-biggestdev

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