ADBHoney
github.com
- Self-hosted
What ADBHoney is
ADBHoney is a free, open-source, self-hosted honeypot for observing malware and other activity against Android Debug Bridge services exposed over TCP/IP. It is a low-interaction endpoint decoy aimed at devices with port 5555 exposed. The honeypot accepts ADB connect, push, and shell operations. Captured data is redirected to standard output, and uploaded files are saved to disk. Its simulated shell is intentionally narrow: adb shell ls returns a unique response, while other commands return command not found. Native directory listing, an interactive shell, and other advanced commands are not supported. Configuration comes from adbhoney.cfg, which must be beside run.py or at /etc/adbhoney.cfg. The README describes running the Python script or building and running a Docker container, and says CPU and memory use should be fairly low. The repository identifies GPL-3.0 as its license, and the maintainer requests a .pcap file or very exact reproduction steps for protocol-behavior issues. The project is intended for investigating activity against exposed ADB services, not for providing a complete ADB environment.
Who it suits
It suits security investigators monitoring exposed Android Debug Bridge services and malware activity. Deployment is self-hosted, through the Python script or Docker.
Good to know, and what to watch
- Free GPL-3.0 open-source honeypot
- Accepts ADB connect, push, and shell
- Saves uploaded files to disk
- Supports Python or Docker deployment
- Designed for exposed port 5555 activity
- Interactive shell is not supported
- Most shell commands return command not found
- Configuration file must be in specific locations
The verdict
ADBHoney offers a focused ADB decoy for collecting activity and uploaded files with limited resource use. Its intentionally restricted shell means it is suited to observation, not full protocol emulation.
What the maker publishes
- ADB commands
- It supports connecting with adb connect, uploading with adb push, and running commands with adb shell. source
- Captured data
- Data is redirected to stdout and uploaded files are saved to disk. source
- Configuration
- The `adbhoney.cfg` file must be beside `run.py` or at `/etc/adbhoney.cfg`. source
- Configuration
- The configuration file must be beside run.py or at /etc/adbhoney.cfg. source
- Deployment
- The README describes running the Python script or building and running a Docker container. source
- Deployment
- The project can be started with Python or run using Docker or Docker Compose. source
- Intended users
- The README describes the project for investigating activity against exposed Android Debug Bridge services. source
- Issue reports
- The maintainer asks for a .pcap or very exact reproduction steps when reporting protocol issues. source
- License
- The repository identifies its license as GPL-3.0. source
- License
- The GitHub repository identifies the project as GPL-3.0 licensed. source
- Limitations
- Advanced commands such as native directory listing and an interactive shell are not supported. source
- Limitations
- More advanced commands, including native directory listing and an interactive shell, are not supported. source
- Logging
- Data is redirected to stdout, and files are saved to disk. source
- Maker
- The GitHub profile identifies huuck as Gabriel Cirlig. source
- Protocol
- It accepts ADB connect, push, and shell operations. source
- Purpose
- ADBHoney is a low interaction honeypot designed to catch malware pushed to devices with Android Debug Bridge exposed over TCP/IP. source
- Purpose
- ADBHoney is a low interaction honeypot designed for Android Debug Bridge over TCP/IP. source
- Resource use
- The README says CPU and memory usage should be fairly low. source
- Resource use
- The README says CPU and memory usage should be fairly low. source
- Shell responses
- Only `adb shell ls` currently returns a unique response; other commands respond with `command not found`. source
- Shell responses
- The adb shell ls command has a unique response; other commands respond with command not found unless responses are added in responses.py. source
- Support
- For issues involving protocol behavior, the maintainer asks for a `.pcap` or very exact reproduction steps. source
- Use case
- The project aims to catch malware pushed by attackers to devices with port 5555 exposed. source
Checked against the maker's pages on 8 Oct 2026.