From ff400cb05f5d38018c2cb4db1edca5ba08d18bd6 Mon Sep 17 00:00:00 2001
From: 0i41E <79219148+0i41E@users.noreply.github.com>
Date: Sat, 3 Aug 2024 21:45:56 +0200
Subject: [PATCH] Update readme.md

---
 payloads/interception/Proxquirrel/readme.md | 25 +++++++++++++--------
 1 file changed, 16 insertions(+), 9 deletions(-)

diff --git a/payloads/interception/Proxquirrel/readme.md b/payloads/interception/Proxquirrel/readme.md
index 54ad112..ae74241 100644
--- a/payloads/interception/Proxquirrel/readme.md
+++ b/payloads/interception/Proxquirrel/readme.md
@@ -1,7 +1,7 @@
 # Proxquirrel
 #### Author: 
 
-**Proxquirrel** is a payload designed for the [Package Squirrel MK II](https://shop.hak5.org/products/packet-squirrel-mark-ii) in combination with a HTTP proxy, like [BurpSuite](https://portswigger.net/burp/releases/professional-community-2024-5-5?requestededition=community&requestedplatform=).
+**Proxquirrel** is a payload designed for the [Packet Squirrel MK II](https://shop.hak5.org/products/packet-squirrel-mark-ii) in combination with a HTTP proxy, like [BurpSuite](https://portswigger.net/burp/releases/professional-community-2024-5-5?requestededition=community&requestedplatform=).
 
 This payload will redirect common web ports like 80 and 443 and therefore enables the user to intercept such traffic with an external proxy and tinker with its content.
 
@@ -11,14 +11,21 @@ Before deploying the Squirrel as also the payload, the user has to configure the
 Set `PROXY_ADDRESS` and `PROXY_PORT`. This has to be the proxy (server). 
 The other options are optional and can be changed, if needed. 
 #### BurpSuite
-Start up BurpSuite and navigate to the *Proxy* tab and open up the options.
-BILD
+Start up BurpSuite and navigate to the *Proxy* tab and open up the *Proxy Settings*.
 Here you have to edit the *proxy listener*.
-Set the *bind address* to either the interface accessible by the Squirrel or simply select *All Interfaces*. 
-BILD
+
+![1](https://github.com/user-attachments/assets/875a0ce2-7378-4dc4-8027-d1b2ea7c48a8)
+
+Set the *bind address* to either an interface accessible by the Squirrel or simply select *All Interfaces*. 
+
+![2](https://github.com/user-attachments/assets/af79f9e7-8d2c-4bc0-8e93-57b477ab4299)
+
 *The payload will automatically verify the connection. If the proxy can't be reached, the payload will fall into a loop, until the proxy (server) is accessible.*
 
 For the last step, we have to check *Support invisible proxying* under the *Request handling* tab.
+
+![3](https://github.com/user-attachments/assets/3ae5bbbd-0695-46cd-a076-2a4d30d6feb0)
+
 In this mode, BurpSuite intercepts traffic that is not specifically directed at a proxy. It acts as an intermediary without requiring the client to be configured for a proxy. This is useful for intercepting traffic from devices or applications that do not allow for proxy configuration. (Or in this case, do not know about it)
 
 Traffic to ports 80 & 443 should now be redirected to your proxy.
@@ -30,7 +37,7 @@ To revert the changes on the Squirrel, press the button to perform a cleanup.
 
 ### Opsec Considerations
 Since this payload performs some sort of interception of the targets traffic, the target-user may encounter multiple issues: 
-	- Security warnings about the connection to a web page not being secure.
-	- Not being able to use certain web applications due to HSTS.
-	- Sensitive information may be visible within the intercepted requests and should be handled with care.
-	- The user may be blocked by certain WAF's 
\ No newline at end of file
+- Security warnings about the connection to a web page not being secure.
+- Not being able to use certain web applications due to HSTS.
+- Sensitive information may be visible within the intercepted requests and should be handled with care.
+- The user may be blocked by certain WAF's