# hackerhouse-opensource/gigabyte_elevatepersist architecture

> Architecture diagram of the GitHub repository hackerhouse-opensource/gigabyte_elevatepersist, 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/gigabyte_elevatepersist
- Repository: https://github.com/hackerhouse-opensource/gigabyte_elevatepersist

## Overview

1. Gigabyte_ElevatePersist – This appears to be the “exploit launcher” or main project, which is likely used to set up or trigger the conditions exploited (e.g., preparing the environment or interacting with the scheduled task).
2. atiadlxy – This project builds the DLL that, when written to a specific Administrator %LOCALAPPDATA% folder, is side-loaded by the vulnerable “GraphicsCardEngine.exe” process launched by the scheduled task.

A. Identify the Main Components:
- Exploit Setup/Launcher Component:
– Represent the Gigabyte_ElevatePersist project as the component that initiates the exploit. It may manage the exploitation flow or help set up the environment.
- Malicious DLL Component:
– Represent the atiadlxy project as the DLL designed for side-loading. This DLL takes advantage of the vulnerability by being loaded during the scheduled task execution.
- Scheduled Task and Vulnerable Service:
– Include a node for the Windows Scheduled Task automatically installed by the Gigabyte VGA tool (a sub-component of GCC). Indicate that this scheduled task executes “GraphicsCardEngine.exe” (the vulnerable process).
- Target Process and System Context:
– Include a node for “GraphicsCardEngine.exe”, which gets launched with Administrative rights and is susceptible to loading an external DLL from the %LOCALAPPDATA% path.
- Administrator Environment:

B. Map Out Relationships & Data Flow:
- The “Gigabyte_ElevatePersist” component prepares or interacts with the system to enable the exploit (e.g., by placing the DLL in the appropriate folder).
- The attacker (or administrator running the exploit) deploys the DLL (atiadlxy) into the Administrator’s %LOCALAPPDATA% folder.
- The scheduled task (configured by GCC) launches “GraphicsCardEngine.exe” with high privileges.
- When “GraphicsCardEngine.exe” runs, it side-loads the malicious DLL from the Administrator’s %LOCALAPPDATA% folder, thereby executing attacker-controlled code in an elevated context.
- This chain results in UAC bypass and persistence on all subsequent logins of users with administrative rights.

C. Highlight Architectural Patterns and Technologies:
- Windows Privilege Escalation Flow:
- Use a clear separation between the “exploit builder” (Gigabyte_ElevatePersist) and the injected component (atiadlxy).
- That the project is developed with Visual Studio (as indicated by .vcxproj files and related filters) and is built using C++.

– “Gigabyte_ElevatePersist” for the exploit setup/launcher
– “atiadlxy DLL” for the injected module
– “Scheduled Task (GCC)” for the task that launches GraphicsCardEngine.exe
– “GraphicsCardEngine.exe” as the vulnerable process
– “Administrator Environment (LOCALAPPDATA)” for the folder where the DLL is deposited
– Use rectangles for software components and ellipses for system processes or user environments.
- If space allows, add annotations that briefly describe what each component is doing, e.g., “Inject DLL → triggers side-loading vulnerability.”

- Components are as detailed as possible – include additional nodes if necessary to represent underlying Windows mechanisms (e.g., scheduled task service) or to highlight the persistence mechanism.
- Maintain a clear separation of responsibilities: the exploit setup, the vulnerable path (DLL injection via scheduled task), and the resultant elevated execution.

## Diagram (Mermaid)

```mermaid
flowchart TD
    %% Exploit Delivery Components
    GE["Gigabyte_ElevatePersist"]:::exploit
    DLL["atiadlxy DLL"]:::malicious

    %% System Components
    ADMIN["Administrator Environment (LOCALAPPDATA)"]:::env
    ST["Scheduled Task (GCC)"]:::system
    GCE["GraphicsCardEngine.exe"]:::process
    EP["Elevated Process"]:::process

    %% Exploit Flow
    GE -->|"DeploysDLL"| ADMIN
    DLL -->|"ProvidesDLL"| ADMIN
    ST -->|"Launches"| GCE
    ADMIN -->|"SideLoadDLL"| GCE
    GCE -->|"RunsAs"| EP

    %% Click Events
    click GE "https://github.com/hackerhouse-opensource/gigabyte_elevatepersist/tree/main/Gigabyte_ElevatePersist/"
    click DLL "https://github.com/hackerhouse-opensource/gigabyte_elevatepersist/tree/main/atiadlxy/"

    %% Styles
    classDef exploit fill:#ADD8E6,stroke:#000,stroke-width:2px;
    classDef malicious fill:#FFB6C1,stroke:#000,stroke-width:2px;
    classDef system fill:#90EE90,stroke:#000,stroke-width:2px;
    classDef process fill:#D3D3D3,stroke:#000,stroke-width:2px;
    classDef env fill:#FFFFE0,stroke:#000,stroke-width:2px;
```
