# francisck/danderspritz_docs architecture

> Architecture diagram of the GitHub repository francisck/danderspritz_docs, generated by GitDiagram from its file tree, README and a sample of source files (last updated 2026-06-30). It is an AI-made overview: check details against the source.

- Interactive diagram: https://gitdiagram.com/francisck/danderspritz_docs
- Repository: https://github.com/francisck/danderspritz_docs

## Overview

1. **What this repository is**
   This is a resource bundle for the DanderSpritz ecosystem, not the full framework runtime. It contains command definitions, scripts, Python tasking code, GUI configuration, compiled binaries/drivers, and package-specific payloads for many codenamed capabilities.

2. **Overall architecture**
   The repo is organized as a set of **feature packages**. Each package usually includes:
   - command metadata and aliases
   - display/storage transforms for results
   - Python tasking and data-handler code
   - target-side scripts
   - compiled modules, drivers, or helper tools
   - version files and deployment artifacts

3. **Control plane: commands and transforms**
   The `Commands/CommandLine`, `Commands/Display`, and `Commands/Storage` trees define the operator-facing command surface. XML files describe the command syntax; XSL files format command output for interactive display or storage. `Aliases` map human-friendly names to these command definitions.

4. **Python orchestration layer**
   The many `PyScripts` trees provide the runtime glue. They contain:
   - `Tasking` scripts that build or schedule work
   - `DataHandlers` that parse results into framework objects
   - package libraries under `Lib/.../cmd/...`
   This is the main logic layer that converts operator intent into framework-specific tasks and interprets returned XML/data.

5. **Target-side execution layer**
   The `Scripts`, `PyScripts/Install`, `Modules`, `Payloads`, and `Uploads` directories hold the artifacts that get deployed to targets: DSS/DSI scripts, executables, DLLs, and drivers. Most folders are Windows-centric and split by architecture (`i386`, `x64`) and build flavor (`vc9`, `vc9s`, etc.).

6. **GUI and operator tooling**
   `Gui` contains Java-based client components and configuration for console, file browser, monitor, task manager, terminal, and request/response modules. It depends on the command metadata and display/storage transforms to render framework results in the operator UI.

7. **Core Dsz framework**
   `Dsz` is the broad shared command/runtime layer: common aliases, command XML/XSL, schemas, databases, helper scripts, Python libraries, GUI configs, and Windows payload/module descriptions. It appears to be the central framework layer that many other packages build on.

8. **Operational automation: Ops**
   `Ops` is a large mission-automation layer. It includes:
   - Python tools for survey, collection, parsing, and analysis
   - plugin-style modules for browser artifacts, credentials, network state, PSP/AV checks, and process/environment discovery
   - supporting databases and data files
   - DSS scripts and alias files that bundle these workflows
   It acts like a higher-level operations library layered over the core framework.

9. **Specialized capability packages**
   Several top-level folders are self-contained capability bundles:
   - `Pc` / `Pc2.2` for **PeddleCheap**, the main implant and its loader/payload pipeline
   - `ZBng` for **ZippyBang**, focused on auth, token handling, remote execution, and shares
   - `DSky` / `Darkskyline` for packet capture and capture parsing/filtering
   - `DmGz` / `FlAv` for network-driver based capture/control components
   These packages have their own commands, payloads, uploads, and Python tasking code.

10. **Data flow between layers**
   The typical flow is:
   operator command in GUI/CLI → XML command definition and alias resolution → Python tasking builds framework request → DSS/DSI scripts and modules execute on target → results return as structured XML/data → data handlers and XSL transforms format/store the output.
   That separation is important for diagramming because command authoring, execution, and presentation are distinct stages.

11. **Binary and driver boundaries**
   Compiled artifacts are kept separate from orchestration logic. `Modules/Files*`, `Uploads`, `Tools`, and some `Legacy` directories contain executable modules, loaders, parsers, and kernel drivers. The repo is clearly split between:
   - orchestration/configuration code
   - target-side binaries/drivers
   - post-processing utilities

12. **Cross-cutting conventions**
   Most packages follow the same naming and layout conventions, which suggests the framework is assembled from reusable templates rather than ad hoc scripts. Version XML files (`Version/*.xml`) and package-specific descriptor XMLs are used to bind a package’s command surface, payloads, and release artifacts together.

13. **High-level diagram boundary**
   For an architecture diagram, the most important boundary is between:
   - **operator-side framework components**: GUI, Python tasking, command metadata, transforms
   - **deployed target components**: implants, drivers, payloads, DSS scripts
   - **supporting tooling**: parsers, survey/analysis scripts, databases, and legacy utilities
   This repository primarily documents the resources that connect those three layers.

Main entry points: [`Dsz/Scripts`](https://github.com/francisck/danderspritz_docs/tree/master/Dsz/Scripts) (DSS scripts), [`Dsz/Commands`](https://github.com/francisck/danderspritz_docs/tree/master/Dsz/Commands) (Command defs), [`Dsz/PyScripts`](https://github.com/francisck/danderspritz_docs/tree/master/Dsz/PyScripts) (Framework glue), [`Dsz/Modules`](https://github.com/francisck/danderspritz_docs/tree/master/Dsz/Modules) (Modules)

## Diagram (Mermaid)

```mermaid
flowchart TD

subgraph group_operator["Operator side"]
  node_gui["Gui<br/>operator UI"]
  node_dsz_commands["Command defs<br/>XML/XSL control plane"]
  node_dsz_pyscripts["Framework glue<br/>Python orchestration"]
  node_mcl_lib["MCL libs<br/>Python framework libs"]
  node_dsz_menu["Menus<br/>input/output helpers"]
  node_python_rt["Python runtime<br/>embedded runtime"]
end

subgraph group_target["Target side"]
  node_dsz_modules["Modules<br/>target module specs"]
  node_dsz_scripts["DSS scripts<br/>target scripts"]
  node_dsz_payloads[("Payloads")]
  node_dsz_tools["Tools<br/>binaries"]
end

subgraph group_ops["Mission tooling"]
  node_ops_py["Ops PyScripts<br/>automation python"]
  node_ops_lib["Ops libs<br/>analysis libs"]
  node_ops_scripts["Ops scripts<br/>workflow DSS"]
  node_ops_data[("Ops data<br/>plans and databases")]
end

subgraph group_bundles["Capability bundles"]
  node_pc["PeddleCheap<br/>implant package"]
  node_zbng["ZippyBang<br/>auth/exec package"]
  node_dsky["DarkSkyline<br/>traffic capture package"]
  node_dmgz["DoormanGauze<br/>filter driver package"]
  node_demi["KiSu/DiBa<br/>driver package"]
  node_other_bundles{{"Other bundles<br/>feature packages"}}
end

node_gui -->|"renders"| node_dsz_commands
node_gui -->|"invokes"| node_dsz_pyscripts
node_dsz_commands -->|"drives"| node_dsz_pyscripts
node_dsz_pyscripts -->|"builds requests"| node_dsz_scripts
node_dsz_pyscripts -->|"binds modules"| node_dsz_modules
node_dsz_pyscripts -->|"runs on"| node_python_rt
node_dsz_commands -->|"uses schema"| node_mcl_lib
node_mcl_lib -->|"provides UI helpers"| node_dsz_menu
node_dsz_scripts -->|"loads"| node_dsz_modules
node_dsz_scripts -->|"deploys"| node_dsz_payloads
node_dsz_tools -->|"builds"| node_dsz_payloads
node_ops_py -->|"imports"| node_ops_lib
node_ops_lib -->|"reads"| node_ops_data
node_ops_py -->|"orchestrates"| node_ops_scripts
node_ops_scripts -->|"leverages"| node_dsz_scripts
node_ops_py -->|"extends"| node_dsz_pyscripts
node_pc -->|"registers"| node_dsz_commands
node_pc -->|"installs via"| node_dsz_scripts
node_pc -->|"ships"| node_dsz_payloads
node_zbng -->|"registers"| node_dsz_commands
node_zbng -->|"executes via"| node_dsz_scripts
node_dsky -->|"registers"| node_dsz_commands
node_dsky -->|"loads"| node_dsz_modules
node_dmgz -->|"loads"| node_dsz_modules
node_dmgz -->|"controls"| node_dsz_scripts
node_demi -->|"loads"| node_dsz_modules
node_demi -->|"orchestrates"| node_dsz_scripts
node_other_bundles -.->|"supported by"| node_ops_py
node_other_bundles -.->|"registered in"| node_dsz_commands

click node_gui "https://github.com/francisck/danderspritz_docs/tree/master/Gui"
click node_dsz_commands "https://github.com/francisck/danderspritz_docs/tree/master/Dsz/Commands"
click node_dsz_pyscripts "https://github.com/francisck/danderspritz_docs/tree/master/Dsz/PyScripts"
click node_mcl_lib "https://github.com/francisck/danderspritz_docs/tree/master/Dsz/PyScripts/Lib/mcl"
click node_dsz_menu "https://github.com/francisck/danderspritz_docs/tree/master/Dsz/PyScripts/Lib/dsz/menu"
click node_dsz_modules "https://github.com/francisck/danderspritz_docs/tree/master/Dsz/Modules"
click node_dsz_scripts "https://github.com/francisck/danderspritz_docs/tree/master/Dsz/Scripts"
click node_dsz_payloads "https://github.com/francisck/danderspritz_docs/tree/master/Dsz/Payloads"
click node_dsz_tools "https://github.com/francisck/danderspritz_docs/tree/master/Dsz/Tools"
click node_ops_py "https://github.com/francisck/danderspritz_docs/tree/master/Ops/PyScripts"
click node_ops_lib "https://github.com/francisck/danderspritz_docs/tree/master/Ops/PyScripts/lib/ops"
click node_ops_scripts "https://github.com/francisck/danderspritz_docs/tree/master/Ops/Scripts"
click node_ops_data "https://github.com/francisck/danderspritz_docs/tree/master/Ops/Data"
click node_pc "https://github.com/francisck/danderspritz_docs/tree/master/Pc"
click node_zbng "https://github.com/francisck/danderspritz_docs/tree/master/ZBng"
click node_dsky "https://github.com/francisck/danderspritz_docs/tree/master/DSky"
click node_dmgz "https://github.com/francisck/danderspritz_docs/tree/master/DmGz"
click node_demi "https://github.com/francisck/danderspritz_docs/tree/master/DeMi"
click node_python_rt "https://github.com/francisck/danderspritz_docs/tree/master/Python"

classDef toneNeutral fill:#f8fafc,stroke:#334155,stroke-width:1.5px,color:#0f172a
classDef toneBlue fill:#dbeafe,stroke:#2563eb,stroke-width:1.5px,color:#172554
classDef toneAmber fill:#fef3c7,stroke:#d97706,stroke-width:1.5px,color:#78350f
classDef toneMint fill:#dcfce7,stroke:#16a34a,stroke-width:1.5px,color:#14532d
classDef toneRose fill:#ffe4e6,stroke:#e11d48,stroke-width:1.5px,color:#881337
classDef toneIndigo fill:#e0e7ff,stroke:#4f46e5,stroke-width:1.5px,color:#312e81
classDef toneTeal fill:#ccfbf1,stroke:#0f766e,stroke-width:1.5px,color:#134e4a
class node_gui,node_dsz_commands,node_dsz_pyscripts,node_mcl_lib,node_dsz_menu,node_python_rt toneBlue
class node_dsz_modules,node_dsz_scripts,node_dsz_payloads,node_dsz_tools toneAmber
class node_ops_py,node_ops_lib,node_ops_scripts,node_ops_data toneMint
class node_pc,node_zbng,node_dsky,node_dmgz,node_demi,node_other_bundles toneRose
```

## Components

### Operator side

Command surface, transforms, GUI, and Python orchestration.

- [Gui](https://github.com/francisck/danderspritz_docs/tree/master/Gui): operator UI · Java console and operator modules for viewing commands, results, and target state. · `Gui`
- [Command defs](https://github.com/francisck/danderspritz_docs/tree/master/Dsz/Commands): XML/XSL control plane · Shared command-line definitions plus display and storage transforms. · `Dsz/Commands`
- [Framework glue](https://github.com/francisck/danderspritz_docs/tree/master/Dsz/PyScripts): Python orchestration · Core Python tasking, data handlers, and reusable command libraries. · `Dsz/PyScripts`
- [MCL libs](https://github.com/francisck/danderspritz_docs/tree/master/Dsz/PyScripts/Lib/mcl): Python framework libs · Common MCL object model, tasking helpers, and platform abstractions. · `Dsz/PyScripts/Lib/mcl`
- [Menus](https://github.com/francisck/danderspritz_docs/tree/master/Dsz/PyScripts/Lib/dsz/menu): input/output helpers · Shared menu, alias, and prompt handling for operator workflows. · `Dsz/PyScripts/Lib/dsz/menu`
- [Python runtime](https://github.com/francisck/danderspritz_docs/tree/master/Python): embedded runtime · Bundled Python standard library and overrides used by tooling and framework scripts. · `Python`

### Target side

Deployed scripts, modules, payloads, drivers, and binaries.

- [Modules](https://github.com/francisck/danderspritz_docs/tree/master/Dsz/Modules): target module specs · Module descriptions and compiled module bundles for target execution. · `Dsz/Modules`
- [DSS scripts](https://github.com/francisck/danderspritz_docs/tree/master/Dsz/Scripts): target scripts · Core execution scripts, request handlers, connected workflows, and helper includes. · `Dsz/Scripts`
- [Payloads](https://github.com/francisck/danderspritz_docs/tree/master/Dsz/Payloads): target payloads · Architecture-specific payload descriptions and packaged release artifacts. · `Dsz/Payloads`
- [Tools](https://github.com/francisck/danderspritz_docs/tree/master/Dsz/Tools): binaries · Operator and legacy helper binaries used to build, configure, or analyze targets. · `Dsz/Tools`

### Mission tooling

Automation, survey, parsing, and analysis layers.

- [Ops PyScripts](https://github.com/francisck/danderspritz_docs/tree/master/Ops/PyScripts): automation python · Mission automation, survey, parsing, and analysis scripts. · `Ops/PyScripts`
- [Ops libs](https://github.com/francisck/danderspritz_docs/tree/master/Ops/PyScripts/lib/ops): analysis libs · Reusable ops libraries for command wrappers, survey engines, parsers, and data models. · `Ops/PyScripts/lib/ops`
- [Ops scripts](https://github.com/francisck/danderspritz_docs/tree/master/Ops/Scripts): workflow DSS · Top-level automation workflows and shared includes for ops missions. · `Ops/Scripts`
- [Ops data](https://github.com/francisck/danderspritz_docs/tree/master/Ops/Data): plans and databases · Survey plans, fingerprints, databases, and supporting lookup data. · `Ops/Data`

### Capability bundles

Self-contained feature packages built on the shared framework.

- [PeddleCheap](https://github.com/francisck/danderspritz_docs/tree/master/Pc): implant package · Main implant package with payload pipeline, install scripts, GUI helper, and legacy resources. · `Pc`
- [ZippyBang](https://github.com/francisck/danderspritz_docs/tree/master/ZBng): auth/exec package · Authentication, token duplication, remote execution, and share management bundle. · `ZBng`
- [DarkSkyline](https://github.com/francisck/danderspritz_docs/tree/master/DSky): traffic capture package · Traffic capture and filtering bundle with scripts, filters, modules, and drivers. · `DSky`
- [DoormanGauze](https://github.com/francisck/danderspritz_docs/tree/master/DmGz): filter driver package · Network-driver based control and capture component with install and target artifacts. · `DmGz`
- [KiSu/DiBa](https://github.com/francisck/danderspritz_docs/tree/master/DeMi): driver package · Kernel driver and communications bundle for module load/list/survey workflows. · `DeMi`
- **Other bundles**: feature packages · Additional packaged capabilities such as SQL, Oracle, capture, and legacy exploit resources.

## Connections

- Gui → Command defs: renders · GUI reads command metadata and transforms to present operator actions and results.
- Gui → Framework glue: invokes · GUI-backed actions delegate into Python tasking and data-handler code.
- Command defs → Framework glue: drives · XML command definitions are paired with Python tasking implementations.
- Framework glue → DSS scripts: builds requests · Python tasking assembles DSS/DSI work for target execution.
- Framework glue → Modules: binds modules · Python libs reference module descriptions, payload types, and target capabilities.
- Framework glue → Python runtime: runs on · Framework Python code executes against the bundled interpreter/runtime.
- Command defs → MCL libs: uses schema · Command packages share common input/output and object models through MCL.
- MCL libs → Menus: provides UI helpers · Menu and input/output helpers are part of the shared framework layer.
- DSS scripts → Modules: loads · Scripts activate compiled modules and target descriptions.
- DSS scripts → Payloads: deploys · Target scripts coordinate payload install and release artifacts.
- Tools → Payloads: builds · Tooling produces or packages payload artifacts and helper binaries.
- Ops PyScripts → Ops libs: imports · Ops workflows are structured around reusable analysis and wrapper libraries.
- Ops libs → Ops data: reads · Ops libraries consume databases, fingerprints, plans, and lookup tables.
- Ops PyScripts → Ops scripts: orchestrates · Python automation is paired with DSS workflows and include files.
- Ops scripts → DSS scripts: leverages · Ops workflows layer on top of shared framework request scripts.
- Ops PyScripts → Framework glue: extends · Ops automation reuses the framework Python ecosystem and command abstractions.
- PeddleCheap → Command defs: registers · The package contributes command metadata, display, and storage definitions.
- PeddleCheap → DSS scripts: installs via · PeddleCheap uses DSS install and trigger scripts.
- PeddleCheap → Payloads: ships · The package bundles level-specific payloads and release descriptors.
- ZippyBang → Command defs: registers · ZippyBang defines its command surface through shared command metadata.
- ZippyBang → DSS scripts: executes via · ZippyBang workflows are implemented with target-side scripts.
- DarkSkyline → Command defs: registers · Traffic capture commands are exposed through the shared control plane.
- DarkSkyline → Modules: loads · Traffic capture depends on target modules and driver descriptions.
- DoormanGauze → Modules: loads · DoormanGauze centers on driver-backed target modules.
- DoormanGauze → DSS scripts: controls · Target control and install behavior is implemented in DSS scripts.
- KiSu/DiBa → Modules: loads · KiSu/DiBa packages module and driver descriptions for deployment.
- KiSu/DiBa → DSS scripts: orchestrates · Install, survey, and connected workflows are driven by DSS scripts.
- Other bundles → Ops PyScripts: supported by · Additional capability bundles are typically managed by the ops automation layer.
- Other bundles → Command defs: registered in · Most bundles expose their operator-facing commands through the shared command trees.
