Hashtopolis (server)

Hashtopolis project (s3inlc and contributors) · also known as Hashtopolis; Hashtopussy

Open sourceActive

Latest GitHub release v1.0.1 (2026-09-09), following v1.0.0 (2026-08-05) and release candidates. Commits on master through 2026-10-27 (maintainer commit 2026-10-23; later commits are dependency bumps). Not tested. Agents are a separate repository (hashtopolis/agent-python) that this entry does not cover.

Hashtopolis is an open-source client-server platform that distributes password-cracking tasks, primarily hashcat jobs, across multiple machines. A PHP server with a web interface holds hashlists, wordlists, rules and task definitions, and lightweight Python agents on the worker machines run the tasks and report recovered passwords back. It works on hashes, not devices, and its documentation describes no mobile-forensics workflow.

Facts

Websitedocs.hashtopolis.org
VendorHashtopolis project (s3inlc and contributors)
LicenceOpen source (GPL-3.0 (GPLv3 text in LICENSE.txt; GitHub reports GPL-3.0))
CategoryPassword recovery
FunctionsPassword recovery
Runs onDocker (tested on Ubuntu 22.04 and Windows 11 with WSL2)
PricingFree
UsersResearch, Open-source DFIR community
Last activity2026-10-23 · Latest non-dependency commit to master (fixed migrations order after stack merge); v1.0.1 released 2026-09-09 [github.com]
GitHub activityhashtopolis/server · 1,834 stars · last push 2026-11-10 · latest release v1.1.0 (2026-11-05) · checked 2026-11-10

Capabilities

  • The README describes Hashtopolis as a multi-platform client-server tool for distributing hashcat tasks to multiple computers, with portability, robustness, multi-user support and management of multiple groups as its main development goals. [github.com]
  • The documentation states that the server hosts the web interface and database, distributes files, hashlists and binaries to agents, centralises cracking progress and collects recovered passwords; it runs on PHP with a MySQL or PostgreSQL database. [docs.hashtopolis.org]
  • The documentation states that agents are lightweight Python clients that request work from the server, run cracking tasks with hashcat and report results back. [docs.hashtopolis.org]
  • The documentation lists central management of files such as wordlists and rules, monitoring and task automation, multi-user permission levels, and support for heterogeneous agent hardware; it states that the platform is primarily designed for hashcat but supports other cracking tools and custom attack strategies. [docs.hashtopolis.org]

Limitations

  • The documentation describes Hashtopolis as primarily designed for hashcat, with agents running the cracking tool and the server coordinating tasks. [docs.hashtopolis.org]
  • The README describes Hashtopolis as a client-server tool for distributing hashcat tasks to multiple computers; it mentions no device acquisition or extraction of hashes from phones or backups. [github.com]
  • The User Manual's hashlist page lists a 'Download Report' action (currently only available in the old user interface) and an export of recovered passwords, which concern cracked hashes, not examined devices. [docs.hashtopolis.org]
  • Running it needs a server stack (PHP, MySQL or PostgreSQL) plus an agent installed on each worker machine, per the documentation's description of its architecture. [docs.hashtopolis.org]

Related tools

Sources

  1. GitHub: hashtopolis/server (README) (github.com)
  2. hashtopolis/server LICENSE.txt (GPLv3) (github.com)
  3. Hashtopolis documentation: What is Hashtopolis? (docs.hashtopolis.org)
  4. GitHub: Hashtopolis release v1.0.1 (2026-09-09) (github.com)
  5. GitHub: hashtopolis/server master commit history (github.com)
  6. Hashtopolis documentation: Hashlists (User Manual) (docs.hashtopolis.org)
  7. Hashtopolis documentation: Basic installation (docs.hashtopolis.org)

Reviewed . Spotted an error? See the corrections policy.