# hackerhouse-opensource/artillery architecture

> Architecture diagram of the GitHub repository hackerhouse-opensource/artillery, generated by GitDiagram from its file tree, README and a sample of source files (last updated 2025-03-16). It is an AI-made overview: check details against the source.

- Interactive diagram: https://gitdiagram.com/hackerhouse-opensource/artillery
- Repository: https://github.com/hackerhouse-opensource/artillery

## Overview

1. Artillery – The main UAC bypass module. It implements the bypass by elevating COM objects to write into protected directories (e.g., System32) and launches an auto-elevated process.
2. Elevator – Likely a complementary module that manages the elevated process execution and may provide additional methods for privilege escalation.
3. fxsst – Another module that might be used for integrating the persistence mechanism (via DLL injection) or any other specialized functionality via its own framework.

A. Identify Main Components and Their Roles
- Clearly designate three primary modules: Artillery, Elevator, and fxsst.
- A “Windows Environment” node that represents the target OS platform (e.g., Windows 7, as noted), emphasizing critical system directories like System32 and key OS components (e.g., COM, explorer.exe).
- If needed, add secondary nodes for external payloads or combined modules (such as modules that work with FAX DLL injection) to highlight how persistence is achieved.

B. Establish Relationships and Interactions
- Directional data flows:
- From Artillery to Windows (interaction with elevated COM objects for writing to System32).
- Between Elevator and the auto-elevated process that ultimately runs with administrator privileges.
- From fxsst to explorer.exe (via DLL injection) to establish persistence.
- Dependency order: Artillery initiates the UAC bypass, followed by the elevated execution of Elevator, which then connects to persistence modules (fxsst).

C. Note Architectural Patterns and Design Principles
- Although the project is not built as a classic MVC or microservices architecture, it does follow a modular approach. Each component (as a separate Visual Studio project, as seen from the .vcxproj files) is designed to perform a specific function.
- Separation of concerns. For instance, Artillery handles the bypass, Elevator manages the elevation routines, and fxsst focuses on post-elevation persistence.
- The use of shared frameworks (as indicated by “framework.h” in both Elevator and fxsst) suggests that there is a common baseline or shared utility library. This should be represented as a binding or common module if needed.

D. Include Relevant Technologies, Frameworks, and Libraries
- That the modules are implemented in C++ for the Windows environment.
- Usage of COM object interactions, resource files for Windows applications, and the Visual Studio solution structure.
- If useful, indicate that the project leverages Windows APIs for elevation and persistence, as well as the specifics of auto-elevation via COM objects.

- A section for each module (Artillery, Elevator, fxsst) with labels describing its purpose.
- A central section representing the Windows Operating System, which interacts with each module.
- Use descriptive names such as “Artillery Module (UAC Bypass via COM)”, “Elevator Module (Auto-Elevation Handler)”, and “fxsst Module (DLL Injection & Persistence)”.
- Sequence: Artillery triggers UAC bypass → elevated process launched by Elevator → persistent injection by fxsst.
- Feedback loops if, for example, the persistence module reinforces or monitors the elevated state.
5. Additional Annotations:
- Interactions such as “COM Object Elevation”, “System32 Write Access”, and “DLL Injection”.

## Diagram (Mermaid)

```mermaid
flowchart TD
    %% Modules Section
    subgraph "Modules"
        A["Artillery Module (UAC Bypass via COM)"]:::module
        E["Elevator Module (Auto-Elevation Handler)"]:::module
        F["fxsst Module (DLL Injection & Persistence)"]:::module
    end

    %% Windows Environment Section
    subgraph "Windows Environment (Windows 7)"
        S["System32 (Protected Directory)"]:::system
        P["Auto-Elevated Process (Admin)"]:::system
        X["explorer.exe (Windows Shell)"]:::system
    end

    %% Inter-module Relationships
    A -->|"triggers"| E
    E -->|"launches"| F

    %% Module to Windows Environment Interactions
    A -->|"COM_Object_Elevation"| S
    E -->|"Initiates_Elevated_Process"| P
    F -->|"DLL_Injection"| X

    %% Click Events for Artillery Module
    click A "https://github.com/hackerhouse-opensource/artillery/blob/main/Artillery/Artillery.cpp"
    click A "https://github.com/hackerhouse-opensource/artillery/blob/main/Artillery/Artillery.vcxproj"
    click A "https://github.com/hackerhouse-opensource/artillery/blob/main/Artillery/Artillery.rc"

    %% Click Events for Elevator Module
    click E "https://github.com/hackerhouse-opensource/artillery/blob/main/Elevator/Elevator.cpp"
    click E "https://github.com/hackerhouse-opensource/artillery/blob/main/Elevator/Elevator.vcxproj"
    click E "https://github.com/hackerhouse-opensource/artillery/blob/main/Elevator/framework.h"

    %% Click Events for fxsst Module
    click F "https://github.com/hackerhouse-opensource/artillery/blob/main/fxsst/fxsst.cpp"
    click F "https://github.com/hackerhouse-opensource/artillery/blob/main/fxsst/fxsst.vcxproj"
    click F "https://github.com/hackerhouse-opensource/artillery/blob/main/fxsst/framework.h"

    %% Styles
    classDef module fill:#c1e1c1,stroke:#2e8b57,stroke-width:2px;
    classDef system fill:#f9e79f,stroke:#d4ac0d,stroke-width:2px;
```
