Source code security is crucial, as attacks often target the source code. It is the most valuable asset after years of hard work. If your code falls into the wrong hands, such as competitors or attackers, all your support, marketing, and customer relations efforts will be rendered useless. Java developers are familiar with the scenario where a sold JAR is recompiled with minor changes to circumvent patent or intellectual property protection and then released on the market, resulting in a significant loss of profit.
To protect against such scenarios, there are various source code protection tools for Java, with byte code level protection being the most modern and reliable method. This involves special transformations with the byte code to ensure that the original functionality of the recompiled Java application cannot be restored, similar to how encrypted text cannot be decrypted without the source algorithm.
The term "API" in this context refers to a non-specialized library JAR [+ dependencies] that can be used in various projects and can be sold independently.
The Java Antidecompiler API has been successfully tested on popular Java APIs such as Log5j, JUnit4, commons-email, commons-cli, commons-net, commons-io, commons-lang3, commons-text, BCEL, ASM, and others.
Increasing the size of the protected API can be considered as the thickness of the protective wall for your API, and it is usually not taken into account even if only a small part is used.
It should be noted also that free cheese is only in a mousetrap.

Overview

Java Antidecompiler is an easy-to-use and reliable tool for protecting Java code and resources. It encrypts entire Java jars without altering the byte code, meaning you don't have to worry about modifying variables or workflows. It secures sensitive data in Java classes and resources, including passwords, expiration dates, and system names, making it impossible to extract. This results in reduced customization work and troubleshooting. In addition, using Antidecompiler is very straightforward, as it uses standard Java crypto-algorithms and hash functions for encryption.

Interface

When using Java Antidecompiler, it's as easy as copy and paste, and simpler than using a standard zip wizard program.

Here are the screens to follow:

Screen 1. Enter your serial number the first time you run the program. The serial number will be securely stored in the user directory. The next time you use the program, you will immediately start with Screen 2. If you don't enter a serial number, the Antidecompiler will operate in trial mode with full functionality but will add a watermark to the protected app. Please note that the log file is only printed in trial mode.




After pressing Next button or Enter key Source screen will appear as shown in

Screen 2. Select API jar to protect. You can use here drag-n-drop.




Screen 3. List of packages. Select packages you need and press Next/Enter




Screen 4. List of dependencies. You should add all nessessary dependencies




Screen 5. The last screen - protection process itself. It may take a while depending on the size of the source API jar




Screen 6. Short Info. By pressing Info buttom you will get short info about
Java Antidecompiler. Please send us this data if you have problems




Screen 7. Protected API jar



where:

1 – encrypted API jar invisible for System ClassLoader and decompilers
2 – class after extraction headers for development time
3 – extracted class text (mockup)
4 – callback method for switching ClassLoader’s

We distinguish between compile time when a user can see only class mockups and runtime, where the custom ClassLoader decrypts the API when running the actual classes.


Example.



CMD Simulator.



Output.



Received Email.