Cheat Engine

voidaccess · How do I cheat? Reputation: 0 Joined: 01 Nov 2013 Posts: 9

I just wanted to know if you send packets to games by only reading memory. Can they detect me reading packets or just writing to them.

DELETED_USER · Posted: Sun Nov 03, 2013 2:24 pm Post subject:

In programming, almost everything can be done.

Read this.

atom0s · Posted: Sun Nov 10, 2013 2:16 am Post subject: Re: ReadProcessMemory C++

DELETED_USER · Posted: Sun Nov 10, 2013 2:52 am Post subject: Re: ReadProcessMemory C++

atom0s · Posted: Sun Nov 10, 2013 2:54 am Post subject: Re: ReadProcessMemory C++

DELETED_USER · Posted: Sun Nov 10, 2013 3:44 am Post subject: Re: ReadProcessMemory C++

manc · Posted: Mon Nov 18, 2013 3:02 am Post subject:

Do you guys know any good sources for learning about how games (or any processes I guess) protect their process space? And also how those things are typically circumvented? I'm not even sure what to ask for specifically, but are there any other sites tailored specifically to this, or are there any good materials you guys know of? I dont have alot of experience with Win32 API (been in a linux environment mostly), is there anything I should know/read/learn specifically?

DELETED_USER · Posted: Mon Nov 18, 2013 6:19 am Post subject:

atom0s · Posted: Tue Nov 19, 2013 12:02 am Post subject:

manc · Posted: Tue Nov 19, 2013 1:43 am Post subject:

All these links mention anti-debugging - is that only relevant to finding exploits in static offline applications (for cracking paid apps, etc), or am I totally off on that? What I'm wondering is, if I try and OpenProcess() and then ReadProcessMemory() from a modern server-sided game that has protection, what methods are used to detect that I've read its memory?

Or is your point that knowing how to get around anti-debuggers lets you debug, and therefore allows you to expose vulnerabilities that could allow you to read/write without restriction?

Please correct anything that sounds totally wrong, I'm just trying to piece things together and get some context here. Thanks for the links by the way.

atom0s · Posted: Tue Nov 19, 2013 3:56 am Post subject:

The first layer of protection most (if not all) anti-cheats have is an anti-debug layer. The biggest threat to an application is the ability to debug and disassemble it. Static analysis can only get so much done when the application involves non-static data from a remote source.

Being able to actively block a debugger is going to be the first step to protection.

After that you need to take into consideration there are applications and system settings that could trigger any extended anti-cheat mechanisms.

For example, if you want to block/ban for dll injection you have to be mindful there are harmless applications that inject without a users knowledge. Such applications like:
- XFire
- TeamViewer
- Steam's in-game overlay

A user could load your game through Steam and get themselves banned.

The same goes for reading memory. Reading is generally not something anti-cheats look for. They may block some API to allow ease of memory reading like OpenProcess and ReadProcessMemory but generally anti-cheats don't trigger a ban or anything for reading memory.

At most, they typically only look for modifications to the process like:
- Memory editing.
- Binary alterations.
- Anti-cheat not running / disabled. (Usually with a packet heartbeat or similar.)
- Lack of important service(s) running.

pellik · Posted: Mon Jan 27, 2014 10:17 pm Post subject:

I was just reading that one of the anti-cheats banned people using an ESP hack that just did readprocessmemory and then drew to the screen without otherwise ever touching the protected process. (Scanning all processes maybe? Or a SSDT hook? Lots of possibilities.)

In these games the attacker always wins. You can always find a way to beat their scans, and they can always devise a method specifically to catch you. The only way to win is to stay off their radar.