Fast-Track Mass Client Issues
I'm wondering if anyone can help me with this. So, When I try to implement a mass-client side attack with Fast-Track(v4.0) no exploits get loaded. This may help.
bandannaproof@(none):~$ su -c "fasttrack -i"
Psyco not detected....Recommend installing it for increased speeds.
Your system has all requirements needed to run Fast-Track!
Fast-Track Main Menu:
Enter the number: 4
Mass Client Client Attack
Enter the IP Address you want the web server to listen on: 192.168.1.X
Enter the number of the payload you want: 1
Would you like to use ettercap to ARP poison a host yes or no: yes
What IP Address do you want to poison: 192.168.1.X
Setting up the ettercap filters....
Compiling Ettercap filter...
etterfilter NG-0.7.3 copyright 2001-2004 ALoR & NaGA
12 protocol tables loaded:
DECODED DATA udp tcp gre icmp ip arp wifi fddi tr eth
11 constants loaded:
VRRP OSPF GRE UDP TCP ICMP6 ICMP PPTP PPPoE IP ARP
Parsing source file 'bin/appdata/fasttrack.filter' done.
Unfolding the meta-tree done.
Converting labels to real offsets done.
Writing output to 'bin/appdata/fasttrack.ef' done.
-> Script encoded into 16 instructions.
Filter compiled...Running Ettercap and poisoning target...
Setting up Metasploit MSFConsole with various exploits...
If an exploit succeeds, type sessions -l to list shells and sessions -i <id>
Have someone connect to you on port 80...
Launching MSFConsole and Exploits...
Once you see the Metasploit Console launch all the exploits have someone
connect to you..
<-"Here's the problem no exploits launched"
Press enter to end the Mass Client Attack...
bandannaproof@(none):~$ ps -aux
root 12091 0.6 4.9 9896 6240 pts/2 S+ 17:00 0:00 python ./fast-track.py -i
root 12095 0.1 0.0 0 0 pts/2 Z+ 17:02 0:00 [sh] <defunct>
root 12097 0.0 0.0 0 0 pts/2 Z+ 17:02 0:00 [sh] <defunct>
Those zombies weren't there before I executed Fast-Track only after I issue the arp poison. Even if I don't arp poison still no exploits launced, and the zombies appear. Then only when exit out of Fast-Track no zombies. Oh! Yeah! This still persists after two reinstalls. Any suggestions?