[akanet]

This is because "movfuscation" isn't a practical option for people actually trying to ship binaries that still perform well for customers but resist reverse-engineering. One of the battlegrounds for this sort of thing is the tug of war between game developers and cheat developers, and games still need to perform very well. Things the author mentioned, like address-rewriting at runtime, don't incur a performance penalty.

[doctorwho]

Just rebuild the sensitive portions of your code using movfuscator and leave the performance critical stuff alone. As long as everything is statically linked and you don't do anything stupid like "if (check) unlock()" that can be easily patched, it would make life pretty miserable for the RE crowd.

[ttoinou]

What's wrong with "if (check) unlock()" ? x)

[emiliobumachar]

It can be modified to "if (true) unlock()" relatively very easily, even in binary. No disassembling needed.

[rasz]

tell that to game developers shipping shitty DRM running game code inside a non hardware accelerated VM.