Developer knowledge network · moderated exchange

Społeczność UnreliableCode

Badania programistów, inżynieria wsteczna i społeczność programistów

Knowledge indexNa żywo
4Categories
919Threads
2.8KPosty
Analysis

Stack Frame Unwinding & Return Address Spoofing in x64 Windows Binaries [v2.4 Technical Discussion]

hook_doctor
Hooking Specialist
MEMBER
Rozpustnik: 181
Data dołączenia: Jul 2019
Posty: 21
Dzięki: 50
2 tygodnie temu · Aug 5, 2026 7:28 PM
#1

How modern anti-cheat modules detect injected DLL function calls:

They walk the call stack (RtlVirtualUnwind) from inside native functions. If the return address points to unbacked / dynamically allocated memory outside valid PE module bounds, the thread is flagged.

Return Address Spoofing Strategy:

  1. Locate a jmp rbx or jmp [rsp] gadget inside a legitimate signed Windows system DLL (kernel32.dll or ntdll.dll).
  2. Overwrite the stack return address with the gadget address.
  3. Restore registers upon function completion.

The unwinder sees the call originating 100% from a signed Microsoft system binary!

stack_smasher
Kernel Explorer
MEMBER
Rozpustnik: 111
Data dołączenia: Feb 2019
Posty: 30
Dzięki: 18
2 tygodnie temu · Aug 5, 2026 8:40 PM
#2

Return address spoofing is essential when calling internal game engine methods from an injected DLL. Great breakdown of stack unwinding.

vtable_slayer
Senior Reverser
MEMBER
Rozpustnik: 215
Data dołączenia: Mar 2018
Posty: 86
Dzięki: 61
2 tygodnie temu · Aug 6, 2026 12:30 PM
#3

Masterclass in x64 calling conventions.