Is Hacking Just Memory Editing ?

Are all hacks centered around memory editing? If not could someone give me an example of one thats not. I only ask because i have messed with memory editing and finding the permanent memory addresses for programs confuses me alot rather than their dynamic ones.

Well, the base of any hack is memory reading/writing, since all the game data is stored on the memory, so yeah

Originally Posted by MarkHC

Well, the base of any hack is memory reading/writing, since all the game data is stored on the memory, so yeah

Makes sense, thanks

Originally Posted by h4344

Are all hacks centered around memory editing? If not could someone give me an example of one thats not. I only ask because i have messed with memory editing and finding the permanent memory addresses for programs confuses me alot rather than their dynamic ones.

"Memory editing" is a misnomer. All a computer's actions are done 'in-memory', so it stands to region to change any of these interactions you'd need to "edit the memory" (unless you're starting to get into hacking on-site hardware, not included here). However, there are many flavours of memory editing, the most popular application of the term is for things like changing values at runtime. Things like giving yourself $500000000, where you simply change the literal value of your money to something else.

Then there's also instruction editing, which is another popular choice. All the instructions are loaded into memory for the processor, so it's still technically "memory editing", but it's a far more potent tool than just changing some values so you have a lot of money. Editing instructions changes the way a program works completely. Common terms are "NOP"ing memory, which is essentially just overwriting a set of instructions with the NOP instruction (No Operation Performed (0x90)), so that the processor ignores that block of executable memory when it reaches it.

Hooking is also another common practice, but in most cases is nothing more than some simple instruction editing. Again, changing the way the program behaves by modifying its executable instructions.

I guess I should clarify that all "hacks" (i.e game hacks) aren't comprised of ONLY memory edits. For example popular Menu Hacks that use Direct3D to draw aren't editing memory when they draw the menu. However, the code that does all the drawing etc isn't malicious at all, and isn't a hack in itself, so my original point stands. The drawing code is only executed because the erstwhile "hacker" has memory-edited some instructions to change the way the program behaves (forcing the program to execute his Direct3D functions).

Basically, two ways to manipulate an application to do what you want it to:

1) Manipulate the way it treats data.
2) Feed it data that it misinterprets such that it ends up doing what you desired.

SQL Injection is an example of 2. Buffer-overflows are an example of 2 as well.
Most game hacks are 1.

Trojans and malwares take it a step further. Polymorphic engines another, etc... 'Hacking' in general is a a broad term.

:S If you want me to improvise, just ask.

So, drinking alcohol is like hacking your brain? Is that it?

Originally Posted by .::SCHiM::.

So, drinking alcohol is like hacking your brain? Is that it?

No, because hacking is malicious. Drinking is....delicious.

Originally Posted by .::SCHiM::.

So, drinking alcohol is like hacking your brain? Is that it?

It is exploiting the brain, lol.

Is Hacking Just Memory Editing ?

Post a Reply

Similar Threads

Tags for this Thread