- Joined
- Apr 4, 2009
- Messages
- 898
- Reaction score
- 157
To view the content, you need to sign in or register
When it comes to Gunz, this is a fantastic way to implement some sort of anti-cheat, automatically to any runnable. In the provided project, you'll have to write the x86/x64 assembly to be embedded yourself. Any Windows API functions can't be used without:
a) Referencing some sort of IAT (Volatile).
b) Manually looking up functions (Reliable). This would involve fetching the PEB (For x86, stored at FS:[0x30]; for x64, stored at GS:[0x30]). Grabbing the module list (Varying location in the PEB). Enumerating the module list, comparing name members until the desired module is found. Grab that modules base, enumerate its headers to find the EAT, then walk the EAT until the desired function is located.
Here's a download of the project:
To view the content, you need to sign in or register
Usage is either handing off the filename to work with as the first parameter, or to simply run the executable, and you'll be prompted for it.
Currently, the sample embeds an anti-debugger check in the resulting executable; if a debugger is running, the application will halt execution until it's detached from the debugger.
Last edited:

