• Simple and modular code base making it easy to contribute.
• HTTP and SOCKS5 support for upstream proxy
• Native MITM support
• Full traffic dump (request/responses)
• Traffic Match / Filter with DSL language
• Traffic Match and Replace support
• Traffic replay in Burp

Installation

From Binary

The installation is easy. You can download the pre-built binaries for your platform from the Releases page. Extract them using tar, move it to your $PATHand you're ready to go.

▶ tar -xvf proxify-linux-amd64.tar
▶ mv proxify-linux-amd64 /usr/local/bin/proxify
▶ proxify -version

proxify requires go1.14+ to install successfully. Run the following command to get the repo -

▶ GO111MODULE=on go get -u github.com/projectdiscovery/proxify/cmd/proxify

▶ git clone https://github.com/projectdiscovery/proxify.git; cd proxify/cmd/proxify; go build; cp proxify /usr/local/bin; proxify -version

▶ proxify -h

This will display help for the tool. Here are all the switches it supports.

Open a local proxy on port 8081 and forward the traffic to burp on port 8080

▶ proxify -addr ":8081" -http-proxy http://127.0.0.1:8080

Open a local proxy on port 8080 and forward the traffic to the TOR network

▶ proxify -socks5-proxy socks5://127.0.0.1:9050

Dump all the traffic into separate files with request followed by the response, as default proxify listen to http://127.0.0.0:8080. Custom address and port can be defined using addr flag.

As default, proxied request/resposed are stored in the logs folder.

▶ proxify -output db

Proxify supports embedding DNS resolver to map hostnames to specific addresses and define an upstream dns server for any other domain name

start a local http proxy on port 8080 using an embedded dns server listening on port 53 and resolving www.google.it to 192.168.1.1, all other fqdn are forwarded upstream to 1.1.1.1

▶ proxify -dns-addr ":53" -dns-mapping "www.google.it:192.168.1.1" -dns-resolver "1.1.1.1:53"

This feature is used for example by the replay utility to hijack the connections and simulate responses. It may be useful during internal assessments with private dns servers. Using * as domain name matches all dns requests.

If the request or response match the filters the dump is tagged with .match.txt suffix:

▶ proxify -request-dsl "contains(request,'firefox')" -response-dsl "contains(response, md5('test'))"

Proxify supports modifying Request and Responses on the fly with DSL language.

▶ proxify -request-match-replace-dsl "replace(request,'firefox','chrome')" -response-match-replace-dsl "regex(response, '^authentication failed$', 'authentication ok')"

Replay all the dumped requests/responses into the destination URL (http://127.0.0.1:8080) if not specified. For this to work it's necessary to configure burp to use proxify as upstream proxy, as it will take care to hijack the dns resolutions and simulate the remote server with the dumped request. This allows to have in the burp history exactly all requests/responses as if they were originally sent through it, allowing for example to perform a remote interception on cloud, and merge all results locally within burp.

▶ replay -output "logs/"

A certificate authority is generated for proxify which is stored in the folder ~/.config/proxify/ as default, manually can be specified by -config flag. The generated certificate can be imported by visiting http://proxify/cacert.crt in a browser connected to proxify.

Installation steps for the Root Certificate is similar to other proxy tools which includes adding the cert to system trusted root store.

Proxify can be used for multiple places, here are some common example where Proxify comes handy:-

proxify -addr "127.0.0.1:8081" -http-proxy "http://127.0.0.1:8080"

User Options > Upstream Proxy > Proxy & Port > 127.0.0.1 & 8081

proxify -output chrome-logs -addr ":9999"

/Applications/Chromium.app/Contents/MacOS/Chromium --ignore-certificate-errors --proxy-server=http://127.0.0.1:9999 &

proxify -output ffuf-logs -addr ":9999"

ffuf -x http://127.0.0.1:9999 FFUF_CMD_HERE

Proxify is made with