BattlEye exploit, it shits on their security, literally.
- Run build.bat (this will only work for VS19, or VS17)
- Start an elevated commandline
- Go to the x64/Release directory
- implanter.exe dll_name window_class
In this case: implanter.exe implant.dll R6Game
To find the window's class name, use WinLister.
This exploits a flaw in the user-mode component of BattlEye that should've never even existed to begin with.
By hooking CreateFileW, and checking if the lpFileName parameter contains our file's name then manipulating it to believe that Kernel32.dll is being loaded, we pass their dll checks and land our module inside of it as if it's a legitimate module.
Every injectable library must have an export called "wnd_hk" that handles the WH, then calls the next in queue.
extern "C" __declspec( dllexport )
LRESULT wnd_hk( int32_t code, WPARAM wparam, LPARAM lparam )
{
static auto done_once = false;
const auto pmsg = reinterpret_cast< MSG* >( lparam );
if ( !done_once && pmsg->message == 0x5b0 )
{
UnhookWindowsHookEx( reinterpret_cast< HHOOK >( lparam ) );
done_once = true;
}
return CallNextHookEx( nullptr, code, wparam, lparam );
}The implant is a ready-to-inject example for R6:S that'll enable player icons once in-game. {Usually hidden in the prep-phase}
support for:
- thread creation
- seh, c++ exceptions
- raw detouring without any tricks
- doing literally anything you want
DefCon42, Brit and haram <3
Also credits to the stupid BE team for not implementing a prevention-handler on theirs software.
None.