Simple MuGuard Soruce (not finished)

Re: [Release] Simple MuGuard Soruce (not finished)

That's good release, please try to finish it......

I hope is help many people.
 
Re: [Release] Simple MuGuard Soruce (not finished)

hmm looks familar but i dunno
good work anyway and GL finnishing it
 
Re: [Release] Simple MuGuard Soruce (not finished)

lol nice but result ?
 
Re: [Release] Simple MuGuard Soruce (not finished)

good work, we need anthack for mu!! someone will continue...
 
Re: [Release] Simple MuGuard Soruce (not finished)

wow, very good idea for authentication with serial, very good job, need to continue.
 
Re: [Release] Simple MuGuard Soruce (not finished)

How you get the offsets?

I'm trying to do it using OllyDbg and TSearch without success.

// Offsets from 1.0N main!
DWORD *Main_Serial = (DWORD*)0x0066FEF0;
DWORD *Main_Version = (DWORD*) 0x0066FEE8;
DWORD *Main_WindowName = (DWORD*)0x66FBB8;
 
Re: [Release] Simple MuGuard Soruce (not finished)

u can search for many commands in olly , if u know for one version, there is like 99% chance u will find offsets u want in other version

I have found the serial, now the problem is how hide this from Cheater do not found it and remove the Hook and connect into the server?
 
Re: [Release] Simple MuGuard Soruce (not finished)

mmm i have a problem i have the SAME main 1.0N and is not N is M bcuz of the version:

const char* MyVersion = "22358";

well now it have the same serial and version but with olly i put that offset and it say is out of range? so comebody have the same main for this proyect?
 
Re: [Release] Simple MuGuard Soruce (not finished)

what did you said its true&right but just for the peoples who have hacks from downloading and use it its good no?....
 
Re: [Release] Simple MuGuard Soruce (not finished)

Please have in mind that this protection can be bypassed VERY EASY. This could work as an EXTRA way to protect your server but do not trust your security to a protection based on window titles or name or running process cause both can be changed in seconds.
you can block debuggers from running your dll by a few simple codes like change size of file over 1 GB so debugger will crash,or others like this.Also you can get a good dll protector like Themida or MoleBox(last one) and first the hacker need to crack the dll than to bypass the window.You can build some "stress system" : shutdown the computer when a debugger is found running or editors and your hacker will dont accept to shutdown his computer 1000time just to can apply a patch for skills in town.Or you can do some security for this kind of hack using this sources but instead of pop-up window use a backup file to replace the "hacked" file.

This "MuGuard" is good for the part with check of files with .bmd extension.The other part is not so good because if you dont secure your dll you will get easy hacked by WPE or other hacking applications.
 
Re: [Release] Simple MuGuard Soruce (not finished)

Hack dll? You just need to change stuff at hacks with any resource editor and that's it. No themida can save you from that. Also themida sucks big time with antivirus.

If I change MuPie window title, running process name it will work with no problems and I needed no experience in hacking / programing / debuggers
 
Re: [Release] Simple MuGuard Soruce (not finished)

Hack dll? You just need to change stuff at hacks with any resource editor and that's it. No themida can save you from that. Also themida sucks big time with antivirus.

If I change MuPie window title, running process name it will work with no problems and I needed no experience in hacking / programing / debuggers

Is because most of anti cheats (like the Loe123 one) use windows names and things like that. you must catch the process who try to access to main and block, there are lot of ways to prevent it.
 
Back