DeathWarden - Anti-Detection - Tripwire - Death to Warden
Brief Description
Deathwarden is a specialized tool to avoid detection from Blizzards Warden. Since 6/1 no one using this Scanning engine and its methods has ever been banned in a wave.
Steps to use - Brief overview
Step 1 Open the Scanner
It will now prompt you with "Please Select the wow exe file"
- Click OK and browse your pc to the wow.exe file located inside your world of warcraft directory.
Step 2 Select your bot.
- Click ok and select the bot application .exe file you wish to have it kill/open
Step 3 It will ask if you want your TCIP ACK Frequency changed, Click yes if you want this feature.
-If clicked yes make sure you restart your pc for the effect to take place.
Step 4 your good to go.... everytime from now on it will auto start the scanner and will not ask u again
should you need to redo these settings click the "Reset" button at the top
Here is what my log file looks like
14:45:3 - Setting up Data Tables - Initializing
14:45:3 - Setting up Data Tables - Complete
14:48:24 - Adjusting TCP/ACK Frequency
14:48:27 - Sanitizing Wow Directory
14:48:27 - Sanitizing Complete(Cleared WTF,ERRORS,LOGS,UPDATES)
14:48:27 - Clearing Data Tables before Baseline
14:48:27 - Establishing Baseline for Compairison for the Active Scanner
14:48:27 - Files Scanned for Baseline - 285
14:48:27 - Setting up Warden Killer - Starting
14:48:28 - Setting up Warden Killer - Completed - Injection text length =134000
14:48:28 - Starting Active Scanner - Running
DeathWarden Can be downloaded here:
DeathWarden
Methodology:
- Alters TCPIP ACK Frequency
Theory behind this method is that warden will not be able to scan your packets coming in as they are moving too quickly for it to identify a particular strain.
- Cleanses the Wow Directory of all Error logs, Account Information, Preferences....etc
This prevents cross accounts bieng banned, by clearing account information if one account should be banned, the others that are "sleepers - not botted at the moment but on hold should they be needed" will not be seen in the account cache. This is not necessary for detouring warden just a nice feature to start off each session with a clean slate.(mostly added for maintenance and detouring detection from error logs etc)
- Active Directory Tripwire
The moment a file is detected to have changed - live updated - or altered in any way the scanner will know about it. If it is deemed to be a danger to the bot or the wow account the tripwire is activated instantly killing all bot processes and all wow windows in less than 1 second. Common map updates etc are ignored in the tripwire so that data will not kill all widows.
- Corruption of the Warden Memory Scanner
Theory behind this is that Warden utilizes dlls for upper memory scanning as this would be too difficult to implement into the main wow.exe, by studying the dlls that contain features that may assist warden. By corrupting these DLL files the fail safe is triggered and wow tries to stream a new copy from the main servers....however that fails too, over and over again. If it cannot scan your PC you cannot be detected by warden.
The Story behind this program:
On 6/1 I was hit in a ban wave using another bot, I had suffered minor waves before however this one really made me mad. So as a programmer I started researching why I was caught, and when I delve deeper I found a way to hinder wardens ability to scan the pc.....thus the Original SpiderScan was born. Since 6/1 that bot program had recieved 4 major ban-waves of which no one using the SpiderScan was banned even while botting through the wave..
.