Obfuscating C++ executors?

Adapted one of Douggem's OnEachFrame executors to work with the offsets for 0.55 and I'm pretty sure it's working but I want to make sure BattlEye can't read it. What would be recommended for that? Obfuscating? MD5 Hash Changers? A combination of both?

What exactly is required to make a C++ hack "BattlEye-Proof"?

As far as I was aware, they stopped OnEachFrame from executing... And the only way to make a hack "battleye proof" is by keeping it private and changing the signature frequently.

You're right, by the way, OnEachFrame is no longer client sided. After talking with Douggem, I found out. Changing signatures? How would you recommend I do that?

And then, would an MD5 hash or some kind of name changer help me stay undetected?

Originally Posted by tweedash

Yes the idea is to change the hash of the file(assuming Battleye hashes the whole file and doesn't find some unique function or section inside it). If Battleye isn't hashing the whole file then something like VMProtect might help. Basically, anything you try can only help you so take whatever steps you'd care to to stay undetected and the worst case scenario is you wasted a few minutes on something that didn't matter.

Originally Posted by Daniel Jackson

Yes the idea is to change the hash of the file(assuming Battleye hashes the whole file and doesn't find some unique function or section inside it). If Battleye isn't hashing the whole file then something like VMProtect might help. Basically, anything you try can only help you so take whatever steps you'd care to to stay undetected and the worst case scenario is you wasted a few minutes on something that didn't matter.

What Daniel said, there's also a lot of packers out there for C++ executable. UPX, VMProtect, Enigma, etc.

Gotcha. I got global banned a couple days ago so I'm putting the project off for now but once I get a new copy I'll keep that in mind. Thanks!

Originally Posted by tweedash

Gotcha. I got global banned a couple days ago so I'm putting the project off for now but once I get a new copy I'll keep that in mind. Thanks!

Anytime. Believe this is solved.
/Closed

Obfuscating C++ executors?

Post a Reply

Similar Threads

Tags for this Thread