Skip to content
Dynamic analysis of Android apps
Python Java
Branch: master
Clone or download

Latest commit

Fetching latest commit…
Cannot retrieve the latest commit at this time.


Type Name Latest commit message Commit time
Failed to load latest commit information.
APIMonitor upload droidbox23 and APIMonitor Sep 25, 2012
droidbox23 upload droidbox23 and APIMonitor Sep 25, 2012
droidbox4.1.1 Update Sep 25, 2015
external No commit message Mar 26, 2012
taintdroid Changs for RC Oct 13, 2011
tests Changs for RC Oct 13, 2011 Update Dec 17, 2019


DroidBox is developed to offer dynamic analysis of Android applications. The following information is described in the results, generated when analysis is complete:

  • Hashes for the analyzed package
  • Incoming/outgoing network data
  • File read and write operations
  • Started services and loaded classes through DexClassLoader
  • Information leaks via the network, file and SMS
  • Circumvented permissions
  • Cryptographic operations performed using Android API
  • Listing broadcast receivers
  • Sent SMS and phone calls

Additionally, two graphs are generated visualizing the behavior of the package. One showing the temporal order of the operations and the other one being a treemap that can be used to check similarity between analyzed packages.


This is a guide to get DroidBox running. The release has only been tested on Linux and Mac OS. If you do not have the Android SDK, download it from The following libraries are required: pylab and matplotlib to provide visualization of the analysis result.

  • Export the path for the SDK tools
export PATH=$PATH:/path/to/android-sdk/tools/
export PATH=$PATH:/path/to/android-sdk/platform-tools/
  • Download necessary files and uncompress it anywhere
  • Setup a new AVD targeting Android 4.1.2 and choose Nexus 4 as device as well as ARM as CPU type by running:
  • Start the emulator with the new AVD:
./ <AVD name>
  • When emulator has booted up, start analyzing samples (please use the absolute path to the apk):
./ <file.apk> <duration in secs (optional)> 

The analysis is currently not automated except for installing and starting packages. Ending the analysis is simply done by pressing Ctrl-C. A package will also be implemented soon to populate the emulator with data prior to performing analysis.

You can’t perform that action at this time.