How rudrakadel/honeypie works
Project type and purpose
• HoneyPie is a Python-based honeypot suite—a security research tool that emulates vulnerable SSH and HTTP services, captures attacker behavior, and optionally presents a web dashboard for analyzing logs.
File structure
• Top-level scripts:
• honeypy.py – CLI entry point; launches SSH and/or HTTP honeypots based on flags
• ssh_honeypot.py – Paramiko-based fake SSH server
• web_honeypot.py – Flask-based fake WordPress admin panel
• Templates directory:
• templates/wp-admin.html – HTML for the fake login page
• log_files directory:
• Stores JSON/plain-text logs of credentials, commands, IPs
• Config/build scripts:
• requirements.txt – dependency list
• .gitignore
• Documentation:
• readme.md, HoneyPie.pdf, Web_Based_Honeypot.pdf
README for insights
• Key components: SSH honeypot, HTTP honeypot, logging & analysis, optional web dashboard
• Technologies: Paramiko (SSH), Flask (HTTP + dashboard), JSON files for storage, basic HTML for dashboard
Main components in the system design
a. External Threat Actors – the “users” (attackers/bots) generating SSH and HTTP traffic
b. SSH Honeypot Service
• Built on Paramiko
• Listens on a configurable port (e.g., 2222)
• Logs authentication attempts and commands to log_files/
c. HTTP Honeypot Service
• Flask app serving wp-admin.html
• Captures POSTed credentials and logs to log_files/
• Implements a tarpitting mechanism to slow attackers
d. Log Storage
• log_files/ (JSON/plain-text)
• Creds logs, HTTP audit logs, funnel logs, command logs
e. Web Dashboard (Optional)
• A separate Flask app (web_honeypot.py or web_app.py per README)
• Reads log_files/ and renders analytics pages (charts, tables)
f. Dev / Ops Environment
• Virtual environment (venv)
• SSH key generation (static/server.key)
Relationships & Interactions
• Attacker → [SSH Honeypot] → Logs directory
• Attacker → [HTTP Honeypot] → Logs directory
• Dashboard → Reads logs → Displays metrics
• CLI (honeypy.py) orchestrates launching SSH and/or HTTP honeypot services
Architectural patterns & design principles
• Modular services: SSH and HTTP honeypots are separate modules
• Single-host microservices style—each service listens on its own port
• File-based persistence (simple JSON/log files) for portability
• Tarpit pattern: intentionally slow responses to waste attacker resources
Final checklist
• Labels for ports (e.g., SSH:2222, HTTP:5000) if desired
• Annotations for tarpit, Paramiko, Flask, JSON logs