unstoppable botnet

botnet that cant be stopped
----------------------------

On first run/installation(sending very few just to establish a host)
--------------------------
a) run upnp script to open port and web check/performance check : else die
b) web downloads MySql and installs silent MSIEXEC /qb /i %SystemDrive%\disks\sw\mysql\mysql_server.msi"
c) runs initial sql script for initial schema
d) installs IIS express 7 and installs ASP.NET website
e) installs metasploit / perl
f) sets itself as the host,and post hostname and flag as host in mysql db


Second run(send out as many as you want,host to connect to hard coded with the established host above (or if u have a few) in itself)
-----------
a) run upnp script to open port and performance check if it can host and flag itself to host if it can one as well at some point down the road if the main host drops
b) if it can dual host/client it installs web downloads MySql and installs silent MSIEXEC /qb /i %SystemDrive%\disks\sw\mysql\mysql_server.msi"
 and runs sql script and IIS Express 7 : else just a client
c) installs metasploit / perl
d) reads registers with host(client only or both)
e) reads from host copies all hosts/clients locally in text file (very important for loss of host) this must run on a timely manner
f) reads command from host (whatever u intend to do)


Bot options
------------
1) self upgradable on command (controlled by version number to match compatibility with clients)
2) all options are controlled by the coder, at the start basic DDoS  weeeeeee
3) any dual purpose clients copy db and asp files from current host on a set basis, if we lose our main host
4) /bin folder for exe's dll's that cannot incorporate into its own source(outside material/scripts and self upgrade
5) /metasploit for metasploit scripts
6) /db for database on host capable clients
7) /perl for perl scripts
8) /www for asp.net sites on host capable clients
9) /peers for txt file on all peers updated frequently



on loss of host
-----------------
1)  read most updated local txt file of peers and scan host bots until one accepts register
2)  bots that are host capable will self communicate to known host capable bots and one with most uptime will take over where everything left off


installation methods
---------------------
1) social engineering
2) 0days
3) I have one but im not tellin  ;x  but its why the .NET 2.0 restriction is required and i am doing it this way


Restrictions
------------
1)  Win32 only, unless u are going to have a mono dropper, but the hosting, appache, will havev to be done yourself
2) .Net 2.0 required on victim (or mono)



Comments?
cio@wow.com

Michael Evanchik
mcbain

free dolan


greets
-------
illwill
graf
koin
IRS
0din
lynx