Right.
In this video, I'm going to demonstrate using proxy fire on Windows with the
SOCKS proxy.
I've already got, a beacon running here and the SOCKS
proxy running the same as the, last video.
Now on my attacker Windows VM,
I'm gonna go down to Proxify,
and I'm gonna run it as a local admin.
And then it, pops up down here.
And the first thing we have to do is
specify a proxy server.
So the address is ten ten five fifty, which is
the team server, and the port is ten eighty.
The protocol is SOX four.
And we can say, no. We don't want that as the default.
And we say yes to creating some proxy fire rules.
So let's hit add,
and I'll just call this, let's just call it tools.
So you can choose a specific application or more
than one application, but I'll just leave it as any.
The target hosts will put ten ten one twenty
dot zero slash twenty four
and ten ten one two two zero slash twenty three.
So these are the subnet ranges for,
dev and cyberbiotic.
Port, I will also use, keep as any, and then the action
will choose the SOCKS proxy that we just defined.
So we can hit okay and okay.
So what I'm gonna do now is start a new terminal window as a local admin,
and I'm going to run MMC with some domain credentials.
So let's say run as net only,
and the user is dev b farmer,
and we will start MMC dot x e.
The password is Superman.
Now we can do control m to add the snap in.
And let's specify the,
the ADUC snap in.
And then the first thing we wanna do is right click this
and say, change domain,
and we'll put in dev dot cyberbotik
dot I o, and hit okay.
And in your proxy window, you should see the,
process here.
And this lets you know that,
proxy fire has picked up the traffic,
and then it's sending through the proxy.
And you have these logs down here
that just gives you an indication of how much data is
going, backwards and forwards.
We can
begin to drill down into these,
and we can see everything from users
two workstations,
So on and so forth.
So that's an example of how to use proxy fire to proxy
aduc through a socks proxy.