[JavaProfit]

Hi. I have no intentions of writing any malicious software with what I am asking, but I'll ask anyways.

I've heard that some decompilers are flawed in the way that you can change goto to goto w or something and hide blocks of code. Are there any other, more practical ways of hiding code from decompilers?

I'm thinking this would be a good way to obfuscate code without having to obfuscate with ProGaurd or similar.

Basically I want the knowledge of how to hide static or instance initializers from most decompilers.

Thanks to all who can assist!

edit: forgot to include the research that I've conducted on my own. It seems that changing goto -> goto_w can work. I was looking at the jsr operator, and possibly the jsr_w operator may work (but I have not tested it). Maybe jump to a subroutine (jsr operator) and then goto_w to some hidden code?

[JavaProfit]

Using a bug in 3rd party software as an argument for security is the silliest idea I've heard in a long time. There's a reason good obfuscators are expensive. ;)

This is targeted towards services that have staff who examine uploaded JARs with public deobfuscators. As in, no the goal is not to obfuscate the code but instead hide some initializes in order to get past these examinations. And run stuff that otherwise would not get approved.

[JavaProfit]

This was posted on the Admincraft subreddit.

May or may not be what I was referring to in my post. Didn't want to link it.

[JavaProfit]

Since the CPU runs machine code, which can also be derived from assembly code, couldn't you use a program such as OllyDBG and bypass the obfuscators? Correct me if I am wrong or if this is just plain silly.

xD

You generally wouldn't use OllyDBG on bytecode...At least that's my stance. You can use it, but javap would give you more detailed information than a disassembly.