Malicious Code Injection in rigid_hoverfly_z3n: A Threat to npm Ecosystem
Summary
MAL-2025-90133: Malicious code in rigid_hoverfly_z3n (npm). Affected versions are not published. No fix is published. How to fix ↓
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.
No signup required · Results in about 60 seconds
Background
The package 'rigid_hoverfly_z3n' 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 floods the npm registry with harmful packages, potentially compromising the integrity of applications that depend on it.
Vulnerability Detail
The vulnerability in 'rigid_hoverfly_z3n' stems from its association with the tea.xyz token reward campaign, which aims to manipulate the npm registry. The malicious code embedded in this package 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 leads to the continuous republishing of variants, polluting the npm registry and posing a risk to developers who unknowingly use these packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall rigid_hoverfly_z3nIf 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 'rigid_hoverfly_z3n' and replace it with a known, secure alternative. Always review the packages you include in your project for any signs of malicious behavior.
Conclusion
The 'rigid_hoverfly_z3n' package poses a significant risk due to its malicious code designed to manipulate the npm registry. Developers are advised to remove this package and remain vigilant about the packages they use. Utilizing tools like Vulert can help in monitoring and alerting for such vulnerabilities in real-time.
See every vulnerability recorded for rigid_hoverfly_z3n →
FAQ
The vulnerability involves malicious code that modifies package.json and repopulates the npm registry with harmful variants.
You can use Vulert, which monitors open-source vulnerabilities in your software. Visit Vulert Scanner to check your application without needing to sign up.
You should uninstall the package immediately using 'npm uninstall rigid_hoverfly_z3n' and review your dependencies for any other potentially harmful packages.
No patches are available for this package as it is considered malicious. The best course of action is to remove it from your project.
Regularly audit your dependencies, use trusted sources for packages, and consider using tools like Vulert to monitor for vulnerabilities in real-time.
