Hi d00ds
I recently looked a bit into the functionalities of warden. As we all know, warden scanns mostly your active tasks lists and temporary files of windows, ram etc.
So even if we rename our pirox.exe to whatever.exe warden _will_ detect it, cause it will recognise an exact sheme of memorie usage that is unique on pirox(pirox ist just the example for now).
Now "a" solution:
First we'll do the basic stuff: We open our bot with a hex.editor. A good one is hiew(my choice). We now try to replace Stuff like windows labels etc by searching for the botname and replace it with shit.exe, windows-tuner.exe or whatever(using stuff like firefox.exe or ventrilo.exe is a shit idea! warden knows them and will recognise a usage difference)
Now the advanced stuff:
Many coders are using engines that protect their codes from disassemling. They also use packers to compress binaries while having them still work without unpacking. We will take a advantage of both for now:
1) UPX is a free and open source packer. Apply it on your bot, and so trick warden by changing the sizes and checksums
2) Executable_Undetector is a closed source free app, coded by trojan coders(yes, its safe lol). It was intended to make malware stuff not to be found by virus-scanners, but on this example, it perfectly fits our needs. Exectable_Undetector will obfuscate the whole code by reassembling functions and changing entry points randomly. Apply it on your bot, and you have your complete app-function's memory usage changes.
3) To add this info: There is also a commercial code-obfuscator named "Themida". Themida _is_ better than Executable_Undetector. But since its warez, i cannot post a dlink to it here. If you dont trust Executable_Undetector, buy themida or get it elsewhere.
Now what? Well, now you got anything undetected. For example you may now use _way_ old bots again that usually were quick detected.
Feel free to ask stuff, im just trying to help out peepz :wave: