Droid Hunter is an Android application vulnerability analysis and penetration testing tool designed to help security researchers inspect APK files and identify potential security issues. It combines application metadata inspection, code extraction, decompilation, and pattern-based information leakage detection in one workflow.
The tool supports Android APK analysis, including disassembling application code and extracting Java-related artifacts for further investigation. It can also be used for authorized penetration testing of connected Android devices.

For another Android security project, see AhMyth Android RAT. Use Android testing tools only on applications and devices you own or have explicit permission to assess.
Droid Hunter is hosted on GitHub. Clone the repository and move into the project directory:
git clone https://github.com/hahwul/droid-hunter.git cd droid-hunter
Install the Ruby gems used by the project:
gem install html-table gem install colorize
You may need appropriate Ruby and RubyGems permissions for installation. Check the repository documentation for compatibility requirements before setting up the environment.
Droid Hunter relies on external utilities for Android package analysis. Open config/config.rb and check the configured paths for the tools required by your environment.
# Example paths from the project configuration $p_adb = "/usr/bin/adb" $p_aapt = "/usr/bin/aapt" $p_dex2jar = File.dirname(__FILE__) + "/../ex_tool/dex2jar-0.0.9.15/dex2jar.sh" $p_apktool = File.dirname(__FILE__) + "/../ex_tool/apktool/apktool_2.3.1.jar" $p_jad = File.dirname(__FILE__) + "/../ex_tool/jad/jad" $p_grep = "/bin/grep" $p_unzip = "/usr/bin/unzip" $p_sfilter = File.dirname(__FILE__) + "/../string_filter"
These paths are examples based on the supplied configuration and may not match your system. Verify that each required utility exists and update its path as needed. Tool versions and installation instructions may have changed since this project was released.
Start the application from the repository directory with Ruby:
ruby dhunter.rb
Use the built-in help option to review the commands supported by your checkout:
ruby dhunter.rb --help
Use the APK analysis option to inspect an application package:
ruby dhunter.rb --apk sample.apk
Replace sample.apk with the path to an APK you are authorized to examine. The original usage documentation also lists support for supplying multiple APK filenames, although the exact syntax should be verified against the installed version.
The documented device-testing option is --pentest. Its usage depends on the device identifier and the project’s expected Android Debug Bridge setup.
ruby dhunter.rb --pentest device
Replace device with the appropriate identifier accepted by your version of Droid Hunter. Connect only test devices you are authorized to assess, and verify the command syntax with the help output before running a test.
The project’s original to-do list identified several planned improvements:
These items describe the project’s stated roadmap and should not be interpreted as features available in every release.
The following screenshots from the original article illustrate the tool’s interface:


For additional Android security analysis, explore the forensic toolkit collection for tools and resources that can support broader investigation workflows.
Project repository: Droid Hunter on GitHub