obfuscator VS MinecraftInjectionAPI

Seeing as there are no WebAssembly obfuscators, I decided to try to build Emscripten with an LLVM-based obfuscator. Specifically, I built it using Hikari, which is based on the obfuscator-llvm project. This was built for research purposes and may not be practical in real-world scenarios, but I thought I'd share it here anyways!

Love this topic. I remember Everquest used to checksum areas of memory that were commonly modified from cheats. World of Warcraft used to (possibly still does, it has been forever since I looked at this) inject anti cheat code at runtime.

Obfuscation and deobfuscation is also super interesting. I think overall reverse engineering and figuring out how things work is one of the most interesting things in computer science.

https://github.com/obfuscator-llvm/obfuscator/tree/llvm-4.0/...

https://blog.quarkslab.com/deobfuscation-recovering-an-ollvm...

obsfucator-llvm -- compiler suite that produces obsfucated binaries.

5- Ah, no. https://github.com/obfuscator-llvm/obfuscator/wiki but I see why you said that, I didn't mean to use shitty app to make your code harder to read, I apologise I meant changing the actual binary, use different opcodes mutate the code, etc.. like llvm obfuscator not this shit. but if I were you I would say the same since I didn't clarify this point.

the obfuscator-llvm project is a nice place to look at when introducing yourself to some fundamental obfuscation techniques like control-flow flattening and opaque predicates, which operate on top of assembly instructions and what are called basic blocks.

There's a very healthy ecosystem for cheating at online games, and it doesn't have to involve mouse manipulation. Here's one simple example of it: https://github.com/zortax/MinecraftInjectionAPI