5 comments

[ 2.7 ms ] story [ 17.7 ms ] thread
How is this different from a every other bytecode interpreter (albeit a very convoluted one using x64 for its bytecode)? Am I missing something?
Is this an old technique in game hacking space?
Learned a few things I didn't know about exception handling, like Vectored Exception Handling. If it's possible to somehow have enough permissions to install a generic vectored exception handler that has enough complexity to emulate generic instructions, not sure why the shellcode couldn't just be included there instead.

Maybe someone else will have a follow on regarding some product that does some more complicated processing in a VEH that could be used to implement something that has the same shape as this.

Why is this AI slop here? The "author" deleted his twitter account and added the disclaimer at the top of this post that it's all written by AI and he's not an actual "programmer or reverse engineer".

The fact that nonsense like this gets likes amazes me. You take an emulator, you know a thing whose entire purpose is to evaluate instructions without actually executing them, "bypass" something with overcomplicated and unnecessary hardware breakpoints usage (what exactly is the point of not just catching the access violation instead? Or why do you need to cause an exception at all to emulate the instructions?) and release it with some awful POC that's also AI generated.