Deathwarden ? wtf

[maclone]

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.

Like Skuddles Anti-Warden thing, dunno if it ever worked.

- 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)

ololol delete all settings cuz warden bieng scan them

- 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.

It checks if the new downloaded .dlls in the WoW folder have changed (read method 'corruption') compared to the original one, then goes an hero with it's process and WoW's if a byte is different. (Process.Kill)

- 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.

It writes ['injects', I'm sorry. (wtf)] random shit in Scan.dll and some other one. Then goes back to 'Active Directory Tripwire'.

It does no interaction with WoW's memory itself. Just constantly deleting, for Warden irrelevant, crap in the WoW folder.
In all, it's "LOL DELETE SCAN.DLL AND INSTALL PROCESS GUARD AND BE SAVE FROM WARDEN, OMG BLIZZARD FAILS HARD"

[Nonominator]

Like Skuddles Anti-Warden thing, dunno if it ever worked.



ololol delete all settings cuz warden bieng scan them



It checks if the new downloaded .dlls in the WoW folder have changed (read method 'corruption') compared to the original one, then goes an hero with it's process and WoW's if a byte is different. (Process.Kill)



It writes ['injects', I'm sorry. (wtf)] random shit in Scan.dll and some other one. Then goes back to 'Active Directory Tripwire'.

It does no interaction with WoW's memory itself. Just constantly deleting, for Warden irrelevant, crap in the WoW folder.
In all, it's "LOL DELETE SCAN.DLL AND INSTALL PROCESS GUARD AND BE SAVE FROM WARDEN, OMG BLIZZARD FAILS HARD"

That made total sense.

[Evieh]

That made total sense.

Basically it does bunch of shit but nothing against Warden.

[maclone]

That made total sense.

I commented on each 'method' it uses against warden, describing what it actually does for a few and sightly satirizing the value of this 'protection'.
What is there not to understand.

Also, /closed for it being worthless. Feel free to PM me if you think this thing actually works.