How calebfenton/simplify works
• A Dalvik VM sandbox (smalivm)
• A deobfuscation/optimization engine (simplify)
• A demo and a CLI debugger (demoapp and sdbg)
Project Type and Purpose
• This is a command-line deobfuscation tool and library suite (not a web or mobile front-end).
• It offers a core VM library (smalivm), an optimizer CLI (simplify), a smali debugger CLI (sdbg), and a demo Android app.
File Structure
• Top-level modules (each a Gradle subproject):
– smalivm
– simplify
– demoapp
– sdbg
– simplify/ObfuscatedApp (an Android example)
• The root also holds CI configs, licensing, wrapper scripts, and settings.gradle linking modules.
• Each module has:
– src/main/java or src/main/kotlin (code)
– src/main/resources (config, XMLs)
– build.gradle (build logic)
Key Insights from the README
• smalivm: Executes Dalvik bytecode, builds an execution graph of register/class values.
• simplify: Consumes those graphs, applies passes (constant propagation, dead-code removal, unreflection, peephole), then rewrites the DEX.
• demoapp: Simple Java examples showing how to embed smalivm.
• sdbg: A REPL-style smali debugger built on smalivm that exposes CLI commands.
Main Components
A. smalivm Library
– Parser & Loader (SmaliParser, SmaliFileFactory)
– VirtualMachineFactory → VirtualMachine
– ExecutionContext & ExecutionGraph builder
– Emulation layer (MethodEmulator, opcode handlers)
– Debugger & Breakpoint subsystem
– Configuration loader & framework JAR resources
B. simplify Engine (CLI)
– Launcher / Main
– ExecutionGraphManipulator
– Strategy modules (ConstantPropagation, DeadRemoval, Peephole, Unreflection)
– DEX rewriter / output module
C. CLI Debugger (sdbg)
– Initialize / Main
– REPL loop with commands (BreakCommand, StepCommand, PrintCommand…)
– Hooks into smalivm’s Debugger and MethodExecutor
D. Demo and Example Apps
– demoapp: Java app that invokes smalivm APIs for simple smali methods
– ObfuscatedApp: Android project used as input for simplify
Relationships and Data Flow
• Input Stage:
– User supplies a DEX/APK to the simplify CLI.
• smalivm Stage:
– Simplify calls smalivm to execute methods
– smalivm builds ExecutionGraphs
• simplify Stage:
– The engine applies optimization passes to each graph
– Graph manipulator returns transformed DEX bytecode
– Output is a new, simplified DEX/APK
• Auxiliary Paths:
– sdbg CLI uses smalivm directly for interactive debugging
– demoapp embeds smalivm in a standalone Java application
Architectural Patterns and Principles
• Modular, library-plus-CLI pattern
• Pipeline pattern: parsing → virtual execution → graph generation → graph optimization → code emission
• Strategy pattern for different optimization passes
• Factory pattern for VM, opcode, and class‐loading components
• Separation of concerns: smalivm is pure execution and graph building, simplify is graph analysis and transformation
Don’t Overcomplicate—Break Into Clear Components
• Under smalivm, group sub-packages by function (parsing, execution, context, emulation, opcode, debug, type, configuration)
• Under simplify, group core and strategy packages