evilginx2 icon indicating copy to clipboard operation
evilginx2 copied to clipboard

Added support to different ports than 443 for targets

Open riramar opened this issue 3 years ago • 3 comments

By default, evilginx2 always connect on port 443 for all domains under proxy_hosts. With this patch, if the port is different than 443, you can provide a domain and port as domain under proxy_hosts. It's a ugly patch, but it works. Please check the example below.

proxy_hosts:
  - {phish_sub: 'sub1', orig_sub: 'sub1', domain: 'example.com', session: true, is_landing: true}
  - {phish_sub: 'sub2', orig_sub: 'sub2', domain: 'anotherexample.com:443', session: true, is_landing: false}

riramar avatar Oct 25 '22 19:10 riramar

@riramar do you happen to have an updated version? This currently no longer works

lonewolf-github avatar Sep 02 '23 11:09 lonewolf-github

I used this patch, but I still get this prompt and am still connected to port 443 2025/04/03 15:05:55 [017] WARN: Cannot read TLS response from mitm'd server dial tcp xxxxxx:443: connect: connection timed out

triplexlove avatar Apr 03 '25 07:04 triplexlove

I used this patch, but I still get this prompt and am still connected to port 443 2025/04/03 15:05:55 [017] WARN: Cannot read TLS response from mitm'd server dial tcp xxxxxx:443: connect: connection timed out

You need to provide the port number in your phishlets proxy_hosts configuration.

proxy_hosts:
  - {phish_sub: 'sub1', orig_sub: 'sub1', domain: 'example.com', session: true, is_landing: true}
  - {phish_sub: 'sub2', orig_sub: 'sub2', domain: 'anotherexample.com:8443', session: true, is_landing: false}

riramar avatar Apr 03 '25 13:04 riramar