ProGuard: Real World Example

Posted on October 28, 2014 by Alexey Shmalko
Tags: Java, obfuscation, ProGuard

ProGuard is a free tool for shrinking, optimizing and obfuscating jar files. I’ve used it at work to protect a commercial application from decompilation, especially critical algorithms. (Unlike machine code, Java bytecode is easy to decompile.)

Here I’ll try to describe how I did that.

Step 1. Gathering your jars

The final application consists of many modules. The first step is to pick ones developed by our company into a single big jar that will be processed by ProGuard.

While obfuscating each module separately, you should keep module’s public API untouched so that another module can find necessary classes by name. Processing all modules in one go removes that restriction.

This step is done with maven-shade-plugin. Add the following to your pom.xml:


                        maven-shade-plugin experiences issues shading DLLs.
                        Unfortunately, our application has several.
                        You could also place some modules you don't want obfuscate.

                    <transformer implementation="org.apache.maven.plugins.shade.resource.ManifestResourceTransformer">

                        <!-- This is entry point of your jar -->

Note: If you’re going to provide your jar packed with all dependencies, remember to exclude all these modules.

Step 2. Obfuscating

After we generated our monster jar, it’s time to do the actual job. Luckily, there is maven plugin for ProGuard.

Add the following to your pom.xml after maven-shade-plugin:

        <!-- Our application is so big that ProGuard had ran out of memory -->

        <!-- File with proguard configuration -->

        <!-- Now exclude all modules that are embedded in the jar, so that
            ProGuard won't see a redefinition of each single class.
            You don't have to write down your main module. -->

            <!-- And so on -->

            List external jars your application depends on
            (that not listed in maven dependencies).
            You probably depend on Java runtime (rt.jar).

            JCE stands for Java Cryptography Extension.
            You probably don't need it, but my application does.

The order of plugins is critical. I found that maven runs them from top to bottom if they’re bound to the same phase.

Then add the following proguard.conf:

# Don't obfuscate or remove your entry point
-keep public class com.yourcompany.Main {
    public static void main(java.lang.String[]);

# Suppress warnings from javax.servlet
-dontwarn javax.servlet.**

# Uncomment if you want to have more meaningful backtraces
# Useful for obfuscation debugging
# You absolutely must keep this commented out for production
# -keepattributes SourceFile,LineNumberTable

This configuration should, at least, make ProGuard do its job and obfuscate your application. If you’re lucky enough, and your application works fine—congratulations, you’re done! Go to step 4 now. Otherwise, welcome to the next section.

Step 3. Fixing application

Most probably, your application now crashes with very strange errors. Don’t worry, I’ll try to fix that now.

From this point on you should read ProGuard manual for the description of options.


The number one trouble for obfuscation is a reflection. To load a class dynamically by name you should know its name after obfuscation; otherwise, jre couldn’t find a class for given name. The same applies to dynamically calling methods.

The first option—don’t obfuscate dynamically loaded classes’ names. What could be simpler? Name after processing equals to name before processing. End of story.

Unfortunately, this is not an option for my application. The most critical part is loaded dynamically and forms a complex structure in the form described in almost one thousand XML files.

So, what’s the solution? Obfuscate all occurrences of class names!

ProGuard has an option for that, but it requires all names to be fully-qualified. Fortunately, adapting all XML files opened a way to delete some classes that were copied just to bring them in scope and removed over 21,000 lines.

After that I added the following to proguard.conf:

-adaptresourcefilecontents **.xml

# Also keep - Swing UI L&F. Keep all extensions of javax.swing.plaf.ComponentUI,
# along with the special 'createUI' method.
-keep class * extends javax.swing.plaf.ComponentUI {
    public static javax.swing.plaf.ComponentUI createUI(javax.swing.JComponent);
Wrong solution

I’m not the first programmer who obfuscated our application. The previous one made a horrible, terrifying mistake and I don’t want you to make the same one.

To resolve obfuscated names at runtime, he brought whole obfuscation map (in the form of two files that should be xor’ed) in the final jar, made a special class for resolving original names to obfuscated ones.

In that way, he made this single class the most important link in the anti-decompilation chain.

Don’t do that!

Resource names

Because class’s full name probably changed, loading resources relative to class’s path will fail.

To fix that, just relocate resource to the appropriate place.


Native methods

The issue with native methods is essentially the same as with reflection. Java relies on C function to contain the class name while accessing class fields from C also assumes knowing their names.

While this is theoretically possible to make the necessary transformation of C source code after obfuscation and recompile library, it’s not practical. So, the best solution is just to keep all stuff in classes with native methods unobfuscated.

-keepclasseswithmembernames,includedescriptorclasses class * {
    native <methods>;

# The CPointer field is referenced from dll, keep it
# -keepclasseswithmembers,includedescriptorclasses class com.yourcompany.NativeClass {
#     protected long CPointer;
# }

Step 4. Enabling more obfuscation

At this point, you should have your application up and running. It’s the best time to enable some more obfuscations!

# This option removes all package names.
# with -adaptresourcefilenames it may cause some resource files to clash.
# If that happens, try -flattenpackagehierarchy instead


P.S. Optimizing optimization

Everything was working fine for a while, but after a couple of weeks, processing started to take an enormous amount of time (Jenkins build aborted after 17 hrs building).

After the investigation, I managed to shrink processing time down to 1 minute by disabling single optimization! Please welcome!

-optimizations !code/allocation/variable


I’ll be glad to hear your successful obfuscation story with all the barriers you overcome.

As a bonus for reading so far, here is a list of assumenosideeffects I found on StackOverflow. Unfortunately, I can’t find it again to tell you original author’s name.