GitPedia

Be shellcode tester

BattlEye shellcodes tester

From es3n1n·Updated June 6, 2026·View on GitHub·
·Archived

As you may know battleye loads custom shellcodes for detecting some stuff. \ Well this software is running those shellcodes and dumps every report that was sent. The project is written primarily in C++, first published in 2021. Key topics include: battleye, cpp, gamehacking, reverse-engineering, windows.

be-shellcode-tester

What is this?

As you may know battleye loads custom shellcodes for detecting some stuff.
Well this software is running those shellcodes and dumps every report that was sent.

How's this works?

  • Iterating dir with previously dumped shellcodes and maps it to self mem.
  • Passes 'hooked' GetProcAddress/GetModuleHandleA/send_report functions to shellcode.
  • Reads report and prints info about it.

How's it useful for me?

Imagine your p2c is detected in be-protected game, all you need to do is dump their shellcodes and check your cheat with this tool.

Features:

  • Hookless
  • Parses 9/10 reports(tested only on eft/r6 tho)
  • Both .dll and .exe versions are available
  • Decrypts encrypted reports from shellcodes
  • Decrypts encrypted reports from BEClient2.dll

How can i dump shellcode from game?

Hook GetProcAddress, get mbi of return address and check if it's not a legit module.

Screenshot:

img

Contributing

Any contributions you make are greatly appreciated.

  1. Fork the Project
  2. Create your Feature Branch (git checkout -b feature/AmazingFeature)
  3. Commit your Changes (git commit -m 'Add some AmazingFeature')
  4. Push to the Branch (git push origin feature/AmazingFeature)
  5. Open a Pull Request

Credits:

@es3n1n
@user344

Contributors

Showing top 1 contributor by commit count.

View all contributors on GitHub →

This article is auto-generated from es3n1n/be-shellcode-tester via the GitHub API.Last fetched: 6/29/2026