|
@vm_call | |||||
|
BattlEye has for the past year been detecting unknown cheats using memory heuristics combined with a method known as stack walking:
vmcall.blog/battleye-stack…
|
||||||
|
||||||
|
Carl Schou / vm
@vm_call
|
6. sij |
|
BattlEye developers have not responded to my LinkedIn inquiries so i don't believe they are interested in fixing any of the flaws i mentioned :-(
|
||
|
|
||
|
Carl Schou / vm
@vm_call
|
6. sij |
|
Next article in the BattlEye series will either be on the kernel mode shellcode, the single-stepper shellcode or the beclient2 shellcode (but i have to finish devirtualizing this first), so buckle up !
|
||
|
|
||
|
Douggem
@dougconfere
|
7. sij |
|
Classic. Back in the day he'd int3 game engine functions and check the ret address against a whitelist to make sure dirty hackers weren't calling them, but removed that feature when he added virtualization. Thanks a ton for your work!
|
||
|
|
||
|
Carl Schou / vm
@vm_call
|
7. sij |
|
That was arma specific, right? I remember hearing about that
|
||
|
|
||
|
wacked aka dubya
@fklsdko
|
7. sij |
|
Doesn't that mean that you can add an exception handler with higher priority (worst case: hook ntdll!KiUserExceptionDispatcher) and then parse out the parameters in your handler?
So basically hooking it by catching exceptions?
|
||
|
|
||
|
NoMoreGames
@NoMoreG90492854
|
7. sij |
|
I would use some antivirus to block BattlEye injections into the game process.
|
||
|
|
||
|
Mr Bond 🧢🇺🇸
@WindowsIsBad
|
7. sij |
|
BattleEye’s incompetence made game hacking in Arma 2 so much fun, their was very little you could do with a little script.
|
||
|
|
||
|
Mr Bond 🧢🇺🇸
@WindowsIsBad
|
7. sij |
|
*couldn’t
|
||
|
|
||