diff --git a/mobile-pentesting/android-app-pentesting/README.md b/mobile-pentesting/android-app-pentesting/README.md
index a99f3983f..c4ab077f1 100644
--- a/mobile-pentesting/android-app-pentesting/README.md
+++ b/mobile-pentesting/android-app-pentesting/README.md
@@ -674,6 +674,18 @@ ProGuard is distributed as part of the Android SDK and runs when building the ap
 
 From: [https://en.wikipedia.org/wiki/ProGuard\_(software)](https://en.wikipedia.org/wiki/ProGuard\_\(software\))
 
+### [DexGuard](https://www.guardsquare.com/dexguard)
+
+Find a step-by-step guide to deobfuscate the apk in [https://blog.lexfo.fr/dexguard.html](https://blog.lexfo.fr/dexguard.html)
+
+(From that guide) Last time we checked, the Dexguard mode of operation was:
+
+* load a resource as an InputStream;
+* feed the result to a class inheriting from FilterInputStream to decrypt it;
+* do some useless obfuscation to waste a few minutes of time from a reverser;
+* feed the decrypted result to a ZipInputStream to get a DEX file;
+* finally load the resulting DEX as a Resource using the `loadDex` method.
+
 ### [DeGuard](http://apk-deguard.com)
 
 **DeGuard reverses the process of obfuscation performed by Android obfuscation tools. This enables numerous security analyses, including code inspection and predicting libraries.**