In this video, I'm going to give a brief demo of the SOCKS proxy.
So I have a beacon here running as b farmer.
My check-in is currently three seconds,
and I'm just going to run socks ten eighty.
So this will start a socks four,
proxy.
And you can see that one of the things that it does is it
automatically sets the,
check-in time of the beacon so that it's more interactive.
That has some an offset cost.
So if you want to slow it down,
you have to adjust that back manually.
But with this running, I'm gonna pop over to
well, I'll tell you what.
Let's have a look at the team server first,
and let me just create a new tab here.
So if we look at our listening ports,
the port that I specified here, ten eighty,
is now listening on the team server.
So any proxy where application
has to be pointed at the team server on on this port.
So if we go into WSL,
let's have a quick look at the, proxy chains configuration.
K. So this is already in here by default.
So we have SOCKS four because this is what I started,
the IP address of the team server, and the ports.
Now we can use it with something like, impact it.
So let's say proxychains.
And I'm just gonna say, WMI exec
j king
at ten ten one two two dot thirty,
and his password is quality
one two three.
And then you you can see how the traffic is going through our chains here.
If you see anything other than okay, such as,
timeout or something like that,
then you wanna go back and double check that your proxy
server is running and that the configuration in
the proxy chain's comp file is correct.
And but here we have the shell running, so we can do who am I,
host name,
and there we go.
And that is a very simple way of using Linux tools with a
SOCKS proxy.