We would like to formally announce that F-Secure has stopped further development of the drozer tool. With the amount of testing tools and techniques that have been developed since drozer's inception, it would be near impossible to incorporate everything into one tool.
However, we still think drozer is a good tool for simulating a rogue application. A penetration tester does not have to develop an app with custom code to interface with a specific content provider. Instead, drozer can be used with little to no programming experience required to show the impact of letting certain components be exported on a device.
To help with making sure drozer can be ran on modern systems, a Docker container was created that has a working build of Drozer.
- The Docker container can be found here: https://hub.docker.com/r/fsecurelabs/drozer
- Instructions on building your own Docker container can be found here: https://github.com/FSecureLABS/drozer/tree/develop/docker
drozer (formerly Mercury) is the leading security testing framework for Android.
drozer allows you to search for security vulnerabilities in apps and devices by assuming the role of an app and interacting with the Dalvik VM, other apps' IPC endpoints and the underlying OS.
drozer provides tools to help you use, share and understand public Android exploits. It helps you to deploy a drozer Agent to a device through exploitation or social engineering. Using weasel (MWR's advanced exploitation payload) drozer is able to maximise the permissions available to it by installing a full agent, injecting a limited agent into a running process, or connecting a reverse shell to act as a Remote Access Tool (RAT).
drozer is open source software, maintained by MWR InfoSecurity, and can be downloaded from: https://labs.f-secure.com/tools/drozer/
Linux / OSX
Note: On Windows please ensure that the path to the Python installation and the Scripts folder under the Python installation are added to the PATH environment variable.
Note: On Windows please ensure that the path to javac.exe is added to the PATH environment variable.
Building Python wheel
git clone https://github.com/FSecureLABS/drozer.git cd drozer python setup.py bdist_wheel
Installing Python wheel
sudo pip install dist/drozer-2.x.x-py2-none-any.whl
Building for Debian/Ubuntu/Mint
git clone https://github.com/FSecureLABS/drozer.git cd drozer make deb
Installing .deb (Debian/Ubuntu/Mint)
sudo dpkg -i drozer-2.x.x.deb
Building for Redhat/Fedora/CentOS
git clone https://github.com/FSecureLABS/drozer.git cd drozer make rpm
Installing .rpm (Redhat/Fedora/CentOS)
sudo rpm -I drozer-2.x.x-1.noarch.rpm
Building for Windows
NOTE: Windows Defender and other Antivirus software will flag drozer as malware (an exploitation tool without exploit code wouldn't be much fun!). In order to run drozer you would have to add an exception to Windows Defender and any antivirus software. Alternatively, we recommend running drozer in a Windows/Linux VM.
git clone https://github.com/FSecureLABS/drozer.git cd drozer python.exe setup.py bdist_msi
Installing .msi (Windows)
Installing (Arch Linux/BlackArch)
On BlackArch or any Arch-based linux distribution where BlackArch repository was enabled:
pacman -S drozer
Installing (Arch Linux/AUR)
With any pacman wrapper:
pikaur -S drozer
PKGBUILD (WARNING: out-of-date)
Installing the Agent
Drozer can be installed using Android Debug Bridge (adb).
Download the latest Drozer Agent here.
$ adb install drozer-agent-2.x.x.apk
Starting a Session
You should now have the drozer Console installed on your PC, and the Agent running on your test device. Now, you need to connect the two and you’re ready to start exploring.
We will use the server embedded in the drozer Agent to do this.
If using the Android emulator, you need to set up a suitable port forward so that your PC can connect to a TCP socket opened by the Agent inside the emulator, or on the device. By default, drozer uses port 31415:
$ adb forward tcp:31415 tcp:31415
Now, launch the Agent, select the “Embedded Server” option and tap “Enable” to start the server. You should see a notification that the server has started.
Then, on your PC, connect using the drozer Console:
$ drozer console connect
> drozer.bat console connect
If using a real device, the IP address of the device on the network must be specified:
$ drozer console connect --server 192.168.0.10
> drozer.bat console connect --server 192.168.0.10
You should be presented with a drozer command prompt:
selecting f75640f67144d9a3 (unknown sdk 4.1.1) dz>
The prompt confirms the Android ID of the device you have connected to, along with the manufacturer, model and Android software version.
You are now ready to start exploring the device.
|run||Executes a drozer module|
|list||Show a list of all drozer modules that can be executed in the current session. This hides modules that you do not have suitable permissions to run.|
|shell||Start an interactive Linux shell on the device, in the context of the Agent process.|
|cd||Mounts a particular namespace as the root of session, to avoid having to repeatedly type the full name of a module.|
|clean||Remove temporary files stored by drozer on the Android device.|
|contributors||Displays a list of people who have contributed to the drozer framework and modules in use on your system.|
|echo||Print text to the console.|
|exit||Terminate the drozer session.|
|help||Display help about a particular command or module.|
|load||Load a file containing drozer commands, and execute them in sequence.|
|module||Find and install additional drozer modules from the Internet.|
|permissions||Display a list of the permissions granted to the drozer Agent.|
|set||Store a value in a variable that will be passed as an environment variable to any Linux shells spawned by drozer.|
|unset||Remove a named variable that drozer passes to any Linux shells that it spawns.|
drozer is released under a 3-clause BSD License. See LICENSE for full details.
Contacting the Project
drozer is Open Source software, made great by contributions from the community.
For full source code, to report bugs, suggest features and contribute patches please see our Github project:
Bug reports, feature requests, comments and questions can be submitted here.