schaut mal was ich gefunden habe ...
Quote:
Working more and more on the 'Warden' issue, I finally have come up with some ways to stop the Warden from scanning your computer and to protect yourself from getting caught with it in your memory. Mind you since people are readin this most likely Blizz is also and they proabably are working on a way to fix it.
Thanks goes to Bloody for helping me with ideas Wink
***Note this does not mean running programs will help yourself not get caught, cheating on the server is your risk not mine.***
Since the Warden tool only scans the first bit of memory on a running task, that is most likely the hook and the header describing to a program what the function is.
Well heres solution one.
Warden can scan all it wants, as soon as it runs into a Windows Logon Service what happens? Nothing cause it will bypass it, which is assumingly why it leaves, Dos, HTTP files, Servers, Databases, NetBios.. etc alone.
All you gotta do is run your program as a start up , windows logon service. Sounds stupid right? Theres programs out there that will launch any program into a startup service and change the mask on it to say: Windows Logon Service. Thus Warden will ignore.
The second bit is a little extreme, but if your a hacker than you do what you got to, to survive.
This will take 2 computers. Network, the jist of things.
Computer A (clean computer no hacks)
Computer B (Hacking computer has the hacks on it)
Computer A runs W0W and remote desktop
Computer B runs Remote Admin with shared resources.
Computer B then initiates there hack with shared properties
Computer A accepts the EXE run notification (if optioned)
Computer B than screenviews, run world of warcraft off Computer A while hacking induced it networked off computer B.
Sounds crazy? Im just a crazy guy. have fun, and thanks to whomever stickies and bumps.