New answers tagged


If you want proof-of-concept VM based obfuscator, you can actually skip the virtualization step and bytecode generation step. You can write an interpreter of x86 instructions in x86 assembler so that the implementation is easy. You can add custom instructions one by one later through assembler macros, for example. This is much less complicated process than ...


You will need to go through each of the over 200 instructions, and figure out how to do the "same" thing in your instruction set. So you'll need to see how the stack may be changing, the stack pointer, the program counter, and also if any memory or register changes. For differences like not having enough registers, you could set aside a portion of memory to ...


You can try to use a tool I created called Threadtear to remove those senseless jumps. It is like java-deobfuscator, but with a GUI and support for newer obfuscator versions. Use Generic > Remove obvious flow obfuscation. You can also reobfuscate the class names / method names to get rid of annoying chinese letters.


First off, have you tried the Krakatau decompiler? Krakatau is designed specifically for working with obfuscated Java bytecode, although the decompiler doesn't support lambdas and isn't very user friendly. That being said, renamed identifiers is not something any tool will able to help you with. You'll just have to reverse engineer it and change them to ...

Top 50 recent answers are included