Malicious Code Injection in rubber_hoverfly_z3n: A Threat to npm Ecosystem

rubber_hoverfly_z3n Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-96415: Malicious code in rubber_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

The rubber_hoverfly_z3n package is part of the npm ecosystem, which is widely used for JavaScript package management. This package, like many others, is intended to facilitate the development of applications by providing reusable code. However, it has been identified as part of a malicious campaign that exploits npm's publishing capabilities, leading to significant security concerns.

Vulnerability Detail

The vulnerability in rubber_hoverfly_z3n stems from its association with a malicious campaign that aims to inflate developer reputation scores through the automatic generation and publication of derivative packages. This malicious code modifies the package.json file to remove private flags, alters version numbers, and generates random package names, ultimately polluting the npm registry. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which has flooded the npm ecosystem with compromised packages.

How To Fix

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

npm uninstall rubber_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 remove the rubber_hoverfly_z3n package from your project to mitigate the risk until a secure version is released. Use the following command to uninstall the package: npm uninstall rubber_hoverfly_z3n.

Conclusion

The rubber_hoverfly_z3n package poses a significant security risk due to its association with malicious code designed to exploit the npm ecosystem. It is crucial for developers to take immediate action by updating or removing the package to safeguard their applications.

See every vulnerability recorded for rubber_hoverfly_z3n →

Share this vulnerability

FAQ

rubber_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, which may compromise your application's integrity and security.

You should update the package to the latest version or remove it from your project to avoid potential risks.

You can use tools like Vulert, which monitors your package-lock.json file for 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 signing up.

How To Fix

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

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