Simple MuGuard Soruce (not finished)

[Holy]

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

The best way is memory checking. Hacks must edit some value in main for make it work.
For example WPE PRO is very easy to detect, no Windows Title Name or proccess name, just
need to see WSARecv() API.

WPE PRO injects his module in WSARecv() API, so its very easy to detect it.

 

[zolamu]

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

yea the best method it compare memory of running process and check who run the main.exe
for exampe if it isnt the explorer.exe so give a msg.. like f1x one.. this is anti hack noob version

 

[fenix010203]

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

Help !!!

============== MuGuard - Debug ==============

Assembling: Module1
Module1.asm(147) : error A2006: undefined symbol : TextOut

Errors ocurred.

Complier Easy Code Asm T_T Help

 

[dacharles]

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

mmm yeah but some of the problem of the people is when they try to compile that....and i need how to find the offsets or just someone have the same main used on this proyect?

 

[zolamu]

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

Help !!!

============== MuGuard - Debug ==============

Assembling: Module1
Module1.asm(147) : error A2006: undefined symbol : TextOut

Errors ocurred.

Complier Easy Code Asm T_T Help

you need add GDI to your project..

 

[Hidden]

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

gj leo! Hope someone finishes it