How zblurx/dploot works
Main System Components
• Command-Line Interface (CLI) – Represented by the entry point (dploot/entry.py) which parses user commands and dispatches actions.
• Action Modules – Under the “dploot/action” directory are individual modules (e.g., backupkey.py, blob.py, browser.py, certificates.py, etc.) that implement the various commands. These are the “user triage” commands.
• Triage Modules – Under “dploot/triage” which mirror some actions and run multiple commands together (e.g., triage.py calls the separate user triage tasks, while machinetriage aggregates machine-specific operations).
• Core Library – Under “dploot/lib”, a set of shared utility modules (consts.py, crypto.py, dpapi.py, masterkey.py, smb.py, target.py, utils.py, wmi.py) provide cryptographic routines, DPAPI logic, target connections, and other helper functions.
• Configuration and Build/Project Files – Files like pyproject.toml and the Makefile denote packaging/build instructions, though they are secondary in the runtime architecture.
Component Relationships and Interactions
• The CLI Entry (dploot/entry.py) accepts input parameters (command, target, credentials, etc.) and routes the request.
• Depending on the chosen command, the entry module delegates to a specific action (or triage) module. For example, if a user calls “dploot masterkeys” or “dploot backupkey,” the corresponding module in the “action” folder gets invoked.
• The Action and Triage modules use the functions provided by the Lib modules to perform tasks such as:
• Connecting to remote targets (using modules like target.py, smb.py, wmi.py).
• Handling DPAPI operations (dpapi.py and masterkey.py).
• Cryptographic calculations (crypto.py).
• Parsing or decrypting various data blobs (utils.py).
• There is a clear separation between modules handling user-specific triage (e.g., certificates, browser, credentials) and those handling machine-specific secret extraction (in both the “action” folder and the mirrored “triage” folder).
Important Architectural Patterns or Design Principles
• Modularity – Each discrete DPAPI action (e.g., dumping credentials, certificates, and vaults) is encapsulated in its own module.
• Separation of Concerns – The CLI portion (entry.py) handles interaction and routing while the “action” and “triage” directories implement business logic. The “lib” directory centralizes shared helper functions and low-level cryptography.
• Extensibility – With segregated modules, adding another command (like support for another data source) is straightforward.
• Reuse of code – The crypto and DPAPI decryption routines in the “lib” package are used by multiple action modules.
Detail Relevant Technologies and External Interactions
• Python Language and its associated packaging (as indicated by setup files such as pyproject.toml).
• Remote connectivity protocols for accessing Windows systems (e.g., use of SMB, WMI, RemoteRegistry). These can be noted as external “services” that the tool interacts with to retrieve files or secrets.
• DPAPI decryption logic – The tool relies on internal cryptographic functions (using standard algorithms such as 3DES, SHA) to decrypt secrets.
• Potential integration with tools and workflows (for instance, the use of domain backup keys, masterkey files, either via file input or decrypting on the fly).