ADBHoney vs Heralding
ADBHoney
github.comHeralding
github.comSide by side
| Figure | ADBHoney | Heralding |
|---|---|---|
| Price from | — | Free |
| Free plan | — | Yes |
| Free trial | — | — |
| Open source | — | — |
| Linux | — | Yes |
| Self-hosted | Yes | Yes |
| Plans published | 0 | 1 |
| Spec score · Honeypot Software | 7.1 (#17) | 7.5 (#12) |
| Intended users | The README describes the project for investigating activity against exposed Android Debug Bridge services. | The project describes itself as a honeypot for users who want to collect credentials. |
| License | The GitHub repository identifies the project as GPL-3.0 licensed. | GitHub identifies the project as GPL-3.0 licensed. |
| Purpose | ADBHoney is a low interaction honeypot designed for Android Debug Bridge over TCP/IP. | Heralding is a simple honeypot that collects credentials. |
Plans
In their own words
ADBHoney
ADBHoney is a free, open-source, self-hosted honeypot for observing attacks against Android Debug Bridge services exposed over TCP/IP. It is designed to catch malware sent to devices, including systems reachable on port 5555. The decoy accepts ADB connect, push, and shell operations. Activity is redirected to standard output, while uploaded files are written to disk. Its shell simulation is intentionally narrow: `adb shell ls` produces a unique response, and other commands return `command not found`. Native directory listing and interactive shell sessions are not supported. Configuration comes from `adbhoney.cfg`, placed beside `run.py` or at `/etc/adbhoney.cfg`. Deployment options described by the project are running the Python script or building and running a Docker container. The README says CPU and memory use should be fairly low. The repository identifies GPL-3.0 licensing, and huuck is identified as Gabriel Cirlig. Protocol issue reports should include a `.pcap` or exact reproduction steps.
Heralding
Heralding is a free, self-hosted network honeypot that collects credentials. It runs on Linux and supports FTP, Telnet, SSH, HTTP, HTTPS, POP3, POP3S, IMAP, IMAPS, SMTP, VNC, PostgreSQL and SOCKS5. When a protocol makes them available, its authentication log records usernames and plaintext passwords. It also writes authentication attempts, session summaries and full session data to CSV and JSON Lines files. Session details can include timestamps, duration, source and destination IP addresses and ports, protocol, authentication attempts and protocol-specific auxiliary data. Session log entries are written after sessions end; authentication entries appear once a password has been transmitted. The README describes pip installation on Debian-based systems and Docker deployment using port mapping. Python 3.7.0 or higher is required. For separate packet captures per session, the README points to Curisoum and says it must be enabled in Heralding.yml. GitHub identifies the project as GPL-3.0 licensed.