Malicious Code Injection in head_flyingfish_0xrequest Package
Summary
MAL-2025-103617: Malicious code in head_flyingfish_0xrequest (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 head_flyingfish_0xrequest package is part of the npm ecosystem, which is widely used for JavaScript development. This package, like many others, is intended to facilitate specific functionalities within applications. However, it has been identified as part of a malicious campaign that exploits npm's publishing mechanisms to inflate developer reputation scores through automated scripts.
Vulnerability Detail
The vulnerability in the head_flyingfish_0xrequest package originates from its association with a malicious campaign targeting npm. The package contains scripts that modify the package.json file to remove private flags, alter version numbers, and generate random package names. This behavior leads to the continuous republishing of variants, polluting the npm registry and potentially compromising the integrity of applications that depend on this package.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall head_flyingfish_0xrequestIf 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 head_flyingfish_0xrequest package and look for alternative packages that provide similar functionality without the associated risks.
Conclusion
The head_flyingfish_0xrequest package poses a significant risk due to its malicious code that alters package metadata and repopulates the npm registry with compromised versions. It is crucial for developers to remove this package and monitor their projects for vulnerabilities to maintain application security.
See every vulnerability recorded for head_flyingfish_0xrequest →
FAQ
It is an npm package that has been identified as part of a malicious campaign to manipulate the npm registry.
The vulnerability can lead to the injection of malicious code, which may compromise your application's security and integrity.
You should uninstall the package immediately and look for alternatives to mitigate any potential risks.
Yes, you can use tools like Vulert, which monitors your package-lock.json file for open-source vulnerabilities in real-time.
Yes, you can use the Vulert playground at Vulert Scanner to check for vulnerabilities in your application without any signup.
