This technology includes the Java byte code and resources encryption, custom class and resource loading, and implementation of "detect and reject" tactics for preventing interception and other hacker attacks. Java Antidecompiler uses "keyless encryption". It means that the encryption key is not hard-coded but calculated at runtime and thus can't be extracted from the decompiled code.

Java Antidecompiler work-flow

Java Antidecompiler contains Antidecompiler itself and Java Preloader. Antidecompiler encrypts the whole jar file, adds Preloader to encrypted jar, and makes changes in
Manifest file.

Java Preloader

includes decryptor, class loader and Sonar module. When JVM starts it calls Preloader according to the modified Manifest. Java Preloader calls Sonar module that checks the environment integrity and the presence of hacker attacks. When Sonar detects suspicious changes in JRE or hacking attempts it just stops the program execution. If everything is OK the execution is passed to decryptor and then to class loader. Finally, the main class of the original program is called.

Thus, if usual obfuscators make the reverse engineering time consuming, painful, and complicated enough, Java Antidecompiler makes it absolutely impossible. Additional technological underpinnings of our algorithms can be found here Apology and DZone.