Skip to content
KitploitKITPLOIT
ToolsExploitsBlog
Log in
Submit
ToolsExploitsBlog
Submit

Hacking, PenTest, and Cybersecurity Tools for Your Security Arsenal!

Kitploit is a directory of hacking, cybersecurity, and pentesting tools. Discover the latest project updates to find vulnerabilities, analyze systems, automate testing, and strengthen your security.

FeedsContactPrivacy© 2026 Kitploit

Tool Directory

Categories

View all categories
Loading categories
Aquadecomp — Orchestrates JADX, CFR, Procyon and Vineflower to decompile Android APK/AAB/XAPK/APKS files, with hidden DEX extraction, deobfuscation, signed APK rebuild, ELF analysis and a local REST API. | Kitploit
Tools/GitLabGitLab/droncito/aquadecomp
Android SecurityStatic AnalysisDynamic Code Analysis (DAST)Mobile App PentestingReverse EngineeringMalware AnalysisCryptographyUtilities & FrameworksBinary AnalysisAPI Security
GitLab
1 day agoNot yet reviewed
Share
droncito/aquadecomp

Aquadecomp

Orchestrates JADX, CFR, Procyon and Vineflower to decompile Android APK/AAB/XAPK/APKS files, with hidden DEX extraction, deobfuscation, signed APK rebuild, ELF analysis and a local REST API.

View Repository

Aquadecomp - Multi-Tool Decompilation Orchestrator

CI

Aquadecomp is an Android application decompilation platform that integrates multiple decompilers into a fallback chain, maximizing decompiled code coverage, even in obfuscated apps.

Key Features

Workflow

decompile runs a single flow with all stages connected:

  1. NORMALIZING INPUT - validates the format (APK/AAB/XAPK/APKS) and rejects unsupported files
  2. INSPECTING APK - ZIP structure, DEX, native libs, packers
  3. DECODING MANIFEST - package, version, permissions, main activity
  4. DECOMPILING TO JAVA - JADX as the primary engine, with rescue of missing classes via CFR, Procyon and Vineflower
  5. RECOVERING CODE - decryption of constant strings, class and metadata analysis, and syntax verification with javac on a sample
  6. SCORING CONFIDENCE - 0-100 score per class with levels (Excellent/Good/Acceptable/Poor/Unreliable)
  7. CALCULATING EFFECTIVENESS - overall score with four dimensions and JSON + Markdown reports

Recovery Engines (recovery package)

  • StringDecryptionEngine: converts constant literals into readable strings (new String(new byte[]{...}), new String(Base64.decode("..."))) without altering the rest of the code
  • ClassRecoveryEngine: detects inner, anonymous and empty classes in the source code
  • MetadataExtractor: detects Kotlin metadata, annotations and source files
  • RealCompilationVerifier: verifies a sample of files with real javac, distinguishing syntax errors from dependency resolution errors
  • RecoveryPipeline: orchestrates the engines over all files in sources/; modified files keep a .bak copy

Decompiler Chain

Instead of relying on a single tool, Aquadecomp uses a multi-engine chain:

  1. JADX - Primary engine, produces readable Java code directly from the DEX
  2. CFR - Rescues the classes that JADX could not generate
  3. Procyon - Second rescue engine, specialized in modern Java
  4. Vineflower - Third rescue engine, maintained fork of Fernflower

The rescue engines receive the APK converted to JAR with dex2jar and only process the classes missing from sources/, thus improving coverage without repeating work.

Result: more classes recovered than with JADX alone, with the primary engine maintaining the quality of the rest of the code.

Orchestration of existing tools

Aquadecomp does not reimplement decompilers: it integrates existing tools (JADX, CFR, Procyon, Vineflower, dex2jar, baksmali/smali, d8 and apksig) into a single chain with stopping criteria, fallback, analysis and verification. The value of the project lies in that orchestration: recovery of the missing classes, analysis of results, signature verification and reconstruction of the APK.

The report indicates the engine that generated each file: confidence.classes[].decompiler stores the label per file and confidence.decompilerStats summarizes how many files each engine produced. The label is metadata, it does not enter into the score calculation.

Effectiveness Report

The main flow calculates an effectiveness score from 0-100 with four dimensions:

  • Coverage (40%): classes with code over the total
  • Integrity (25%): decompilation errors and warnings
  • Identifiers (25%): loss of names due to obfuscation
  • Resources (10%): decoded resources and manifest

The detail is output in aquedecomp-report.json (effectiveness) and in the Markdown report.

The verification package also calculates a score per class with levels (Excellent/Good/Acceptable/Poor/Unreliable), which is included in the report under confidence.

Multi-Format Support

  • .APK - Standard Android packages
  • .AAB - Android App Bundles: the DEX files in base/dex/ are read and, if the binary manifest does not exist, the XML decoded by JADX is used
  • .XAPK - Expanded packages: the internal APK (base.apk) is extracted for inspection, manifest and rescue
  • .APKS - APK splits: same as above with base-master.apk

All four formats are validated in the normalization stage; a file that is not a valid ZIP, that does not contain Android content or that has an unknown extension is rejected with a clear message and an error report that is still generated.

Full Analysis

  • Manifest inspection
  • Protector/packer detection
  • Obfuscation analysis
  • Decompilation statistics (classes, errors, lines)
  • Effectiveness report with published methodology

2.0.0: Analysis and Extensibility

  • rebuild - recompiles the decompiled sources and generates a signed APK with the applied changes (v1+v2+v3 signing with its own certificate: installing it requires uninstalling the previous app); detects aquedecomp-mapping.txt to restore the classpath and rename the dex to the original names (see docs/REBUILD.md)
  • --mapping - applies ProGuard/R8 mappings when decompiling to recover classes and members with their original names (see docs/REBUILD.md)
  • serve - local REST API with JSON to decompile, inspect, extract hidden DEX files, recompile, analyze natives and infer names over HTTP (see docs/API.md)
  • natives - real ELF analysis of the package's .so files (sections, exports, imports, dependencies) with optional Ghidra disassembly if installed (see docs/NATIVES.md)
  • Encryption plugins - AES/RC4/XOR decryption when the key is embedded as a literal, with honest notes when it cannot be decrypted (see docs/CRYPTO_PLUGINS.md)
  • nombres - heuristic name suggestions for obfuscated identifiers, report only, without modifying code (see docs/NAME_INFERENCE.md)
  • unpack - extracts the hidden DEX files from a packed APK with static analysis (assets, libs and ZIP/zlib payloads) and repackages the APK with them at the root; decompile runs it automatically when there is no DEX at the root

External tools

  • apkid - identifies packers, protectors and compilers with APKiD (YARA rules on each file in the APK)
  • bundle - converts an AAB into an APKS file with bundletool in universal mode
  • simplify - deobfuscates an APK with Simplify: runs the dex in a smali virtual machine and rewrites the methods
  • deobfuscator - deobfuscates an APK with java-deobfuscator: detects the obfuscator (Zelix, Stringer, Allatori, DashO…), decrypts strings in an isolated sandbox and repackages the signed APK
  • merge - merges split APKs into a single APK with APKEditor (accepts a folder, .apks, .xapk and .apkm)

The bundletool, Simplify, java-deobfuscator and APKEditor jars are downloaded only once to ~/.aquadecomp with SHA-256 verification and can be replaced with the AQUADECOMP_BUNDLETOOL, AQUADECOMP_SIMPLIFY, AQUADECOMP_DEOBFUSCATOR and AQUADECOMP_APKEDITOR variables; APKiD is located in the PATH or specified with AQUADECOMP_APKID. Details in docs/USAGE.md.

Installation

Requirements

  • Java 21+
  • 4GB RAM minimum (6GB+ recommended for large APKs)

Download

The GitLab pipeline builds aquedecomp.jar on every push to main, along with its checksum aquedecomp.jar.sha256. Both are downloaded from the latest green pipeline:

Download Tool

Most Popular

View all →

Discover the most used tools by our community.

  • 1

    OsintHunter

    letox4/osinthunter

    🎯 The ultimate OSINT toolkit: investigation graph, confidence scoring, alias families, map, timeline and reports. 49 modules, 400+ sites, no API keys required.

    491
  • 2

    ghostlock-app

    yukonga/ghostlock-app

    GhostLock One-Tap Execution App (CVE-2026-43499)

    462
  • 3

    opencti

    opencti-platform/opencti

    Open Cyber Threat Intelligence Platform

    345
  • 4

    ARTEX

    baarai/artex

    LLM multi-agent autonomous penetration testing platform with planner/worker agents, asset and exploration graphs, MITM traffic recording, and vulnerability retesting.

    340
  • 5

    redforge

    cybersecurity91/redforge

    Browser-side red team toolkit with 102 offline tools for recon, payload generation, credential attacks, crypto, encoding and engagement reporting.

    306
  • 6

    estorides

    grisuno/estorides

    Aggregates 99+ free OSINT sources in parallel, resolves entities into a knowledge graph, and exports STIX 2.1, MISP, or GraphML with LLM-assisted analysis.

    292

Explore all tools

Browse our collection of tools

View all tools →