Reverse Engineering & Memory Hacking of Packed Programs

Learn how to reverse, debug and patch packed programs - without unpacking - by using Cheat Ee

Bypass anti-debuggers

Patch Memory

Use x64dbg debugger

Using Cheat Ee

Using ScyllaHide Plugin

Using SharpOD Plugin

Using built-in hide Debugger functionality

Using Trainers (Loaders) for Process Patching

AOB Code Injection

Direct Byte Patching

ASM scripting for app hacking

LUA scripting for memory hacking

Designing Trainers (Loaders) with CE's Form Designer

Break and Trace

Modify program behaviour

Packing and Disassembling Crackmes using Popular Packers

..

Assembly language is helpful but not compulsory

Windows PC

Already know how to use x64dbg debugger

Familiar with Cheat Ee

If you had always wanted to learn how to reverse and patch packed programs - without unpacking, then this is the course for you. This course is a follow-up from the earlier course on Reverse Eeering & Memory Hacking. It is the practical application of what you have learnt in the first course. If you think that packing and anti-debugging is good enough to prevent reverse eeering, then you may be in for a surprise. In this course, I will show you how to test the effectiveness of several popular packers by packing crackmes and then reversing them - without unpacking.

Traditionally packed programs are unpacked before debugging is carried out. This is because a packed program's file cannot be patched. Much of software protection has centered on making it difficult to unpack programs. However, the important question is: how effective is packing, obfuscation and anti-debugging as a means to prevent reversing This course explores several packers to find the answers.

We will do the analysis using a tool called Cheat Ee, which is a prominent tool used by game hackers. This tool could also be used to study and analyze packed program's processes that is running in memory. You will learn how to perform debugging in spite of anti-debugging being implemented. There is no need to unpack and dump memory. Instead of unpacking and then patching the dumped files and fixing IAT (Import Address Table) tables, we will write scripts to hack memory using byte patching using an advanced technique called AOB (Array-Of-Bytes) Injection, by injecting code into code caves (inline memory patching). In this course you will learn how to do all of the above

At the end of this course you will be able to gauge the effectiveness of software packers, obfuscation and anti-debugging protection and also to have a good idea of how to implement extra countermeasures to improve the security of software.

In all the practical exercises and walkthroughs, we will use Crackme's which I have written. You will learn how to pack them using several popular packers and then hack them using Cheat Ee.

What you will learn

How to set hardware breakpoints and debug packed programs in spite of anti-debugging protection

Doing Break and Trace to identify Algorithms for reversing

Identifying addresses to do memory patching

Writing custom trainers (loaders) using Cheat Ee to hack and patch memory

Modify program behavior

Process Patching programs

Creating Lua Scripts for process patching

Test the effectiveness of Anti-Debugging technology

Packing crackmes using popular packers

Hack the packed crackmes and patch their memory during run

Prerequisites:

Before taking this course, you should preferably be already familiar with how to use x64dbg and Cheat Ee

Windows PC

Some knowledge of Assembly would be useful but not compulsory

Anyone who wants to know how to assess the effectiveness of packers against Reverse Eeering

Software Developers who want to implement extra layer of protection in addition to packing and Anti-debugging

Reversing hobbyist who wants to level up their skills to take on packed software

An introduction to Software Protection for anyone who wants to get started in this field



DOWNLOAD
uploadgig


rapidgator


nitroflare