Developer knowledge network · moderated exchange

مجتمع الكود غير الموثوق به

أبحاث المطورين، مجتمع الهندسة العكسية والترميز

Knowledge indexيعيش
4Categories
919Threads
2.8Kدعامات
Analysis

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

hook_doctor
Hooking Specialist
MEMBER
مندوب: 181
تاريخ الانضمام: Jul 2019
دعامات: 21
شكرًا: 50
2 weeks ago · 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
مندوب: 111
تاريخ الانضمام: Feb 2019
دعامات: 30
شكرًا: 18
2 weeks ago · 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
مندوب: 215
تاريخ الانضمام: Mar 2018
دعامات: 86
شكرًا: 61
2 weeks ago · Aug 6, 2026 12:30 PM
#3

Masterclass in x64 calling conventions.