# stryker-defense-inc/strykerapp architecture

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

- Interactive diagram: https://gitdiagram.com/stryker-defense-inc/strykerapp
- Repository: https://github.com/stryker-defense-inc/strykerapp

## Overview

##### Project Type and Purpose
- It is an Android mobile application.
- Its primary function is to serve as a pentesting and network vulnerability assessment tool.
- The app integrates multiple penetration testing modules (e.g., exploit hub, metasploit integration, nmap scanning, local network scanning) and uses embedded binary assets (such as busybox, sqlite3, shell scripts) to perform low-level operations on rooted devices.
- The README confirms that the app is intended for users with Android 8.0+, root access (Magisk), and 64-bit CPUs, reinforcing its role as a pentest toolkit.

##### Analyzing the Project Structure
- The top-level “app” directory is the core of the Android project, complete with Gradle build files and AndroidManifest.xml.
- Source code is organized in a hierarchical package structure under com/zalexdev/stryker. Each subpackage groups related features:
– "appintro": Manages introductory screens and user onboarding.
– "coremanger": Likely responsible for central control tasks, managing package installation and execution of pentesting modules.
– "custom": Contains custom exploit and module definitions.
– "exploit_hub": Houses features related to exploitation modules and launching exploits.
– "geomac": Possibly for MAC address-based geolocation or related functionality.
– "handshakes": Manages WiFi handshake collection and related protocols.
– "local_network": Provides tools to scan and engage with devices on a local network.
– "metasploit": Integrates features related to running Metasploit commands (console, utilities).
– "modules": Deals with the installation and management of additional modules.
– "nmap": Integrates network scanning (like using Nmap).
– "router_scan": Implements scanning and interacting with routers.
– "searchsploit": Allows searching and leveraging exploit databases.
– "three_wifi": Likely targets WiFi-related pentesting tasks.
– "wifi": Houses WiFi network management and pentesting utilities.
– "utils": Provides helper classes (e.g., CheckRoot, Logger) and utility functions.
- The assets folder contains various binaries and scripts (busybox, boot_bash, killroot, etc.) that the app uses to perform system-level operations.

A. User Interface (UI) Layer:
– Include Activities and Fragments (e.g., MainActivity, Dashboard, Account, Settings, Exploit and Module screens).
– The "appintro" package forms the initial onboarding flow.

B. Core Manager / Controller Layer:
– Represent the CoreManager (from the coremanger package) as a central coordinating component.
– This layer is responsible for orchestrating tasks, dispatching commands from UI interactions to relevant modules.
– It integrates utility components (from the utils package) like CheckRoot, Logger, and file management classes.

C. Pentest and Exploitation Modules:
– Group modules like exploit_hub, metasploit, local_network, nmap, router_scan, searchsploit, and three_wifi.
– Each module represents a distinct pentesting functionality (e.g., network scanning, exploit deployments, WiFi analysis).

D. Assets and External Tools Component:
– Note that the app embeds many external binaries and scripts in the assets directory.
– Show an “Assets/Utilities” block that supplies the binaries (busybox, sqlite3, various scripts) which the application’s backend modules leverage.

E. Underlying Android Framework and Infrastructure:
– Mention standard Android components such as the application layer, build tools (Gradle scripts), and configuration (AndroidManifest.xml).
– Indicate how these support the operational environment (resource handling, UI rendering, permissions).

##### Relationships and Design Principles
– From UI (user actions) → Core Manager → Pentest Modules.
– From pentest modules → External assets (for command execution).
– Communication between modules if they share common utilities (via the utils package).
– For UI components (e.g., rounded rectangles for screens/activities).

## Diagram (Mermaid)

```mermaid
flowchart TD
    %% UI Layer
    subgraph "User Interface (UI) Layer"
        UI1["MainActivity"]:::ui
        UI2["Dashboard"]:::ui
        UI3["Account"]:::ui
        UI4["Settings"]:::ui
        UI5["Onboarding"]:::ui
    end

    %% Core Manager Layer
    subgraph "Core Manager / Controller Layer"
        CM["CoreManager"]:::core
    end

    %% Pentest Modules
    subgraph "Pentest and Exploitation Modules"
        PM1["Exploit Hub"]:::module
        PM2["Metasploit Integration"]:::module
        PM3["Local Network Scanning"]:::module
        PM4["Nmap Scanning"]:::module
        PM5["Router Scanning"]:::module
        PM6["SearchSploit Module"]:::module
        PM7["Three WiFi Pentesting"]:::module
        PM8["WiFi Utilities"]:::module
    end

    %% Assets & External Tools
    subgraph "Assets and External Tools"
        AT["Embedded Binaries & Scripts"]:::asset
    end

    %% Underlying Android Framework and Infrastructure
    subgraph "Underlying Android Framework and Infrastructure"
        IR1["AndroidManifest.xml"]:::infra
        IR2["Gradle Build Files"]:::infra
    end

    %% Relationships: UI -> Core Manager
    UI1 -->|"initiates"| CM
    UI2 -->|"initiates"| CM
    UI3 -->|"initiates"| CM
    UI4 -->|"initiates"| CM
    UI5 -->|"initiates"| CM

    %% Relationships: Core Manager -> Pentest Modules
    CM -->|"delegates"| PM1
    CM -->|"delegates"| PM2
    CM -->|"delegates"| PM3
    CM -->|"delegates"| PM4
    CM -->|"delegates"| PM5
    CM -->|"delegates"| PM6
    CM -->|"delegates"| PM7
    CM -->|"delegates"| PM8

    %% Relationships: Pentest Modules -> Assets
    PM1 -->|"invokes"| AT
    PM2 -->|"invokes"| AT
    PM3 -->|"invokes"| AT
    PM4 -->|"invokes"| AT
    PM5 -->|"invokes"| AT
    PM6 -->|"invokes"| AT
    PM7 -->|"invokes"| AT
    PM8 -->|"invokes"| AT

    %% Relationship: Core Manager linked to Underlying Android Infrastructure
    CM --- IR1
    IR1 --- IR2

    %% Click Events for UI Layer
    click UI1 "https://github.com/stryker-defense-inc/strykerapp/blob/main/app/src/main/java/com/zalexdev/stryker/MainActivity.java"
    click UI2 "https://github.com/stryker-defense-inc/strykerapp/blob/main/app/src/main/java/com/zalexdev/stryker/Dashboard.java"
    click UI3 "https://github.com/stryker-defense-inc/strykerapp/blob/main/app/src/main/java/com/zalexdev/stryker/Account.java"
    click UI4 "https://github.com/stryker-defense-inc/strykerapp/blob/main/app/src/main/java/com/zalexdev/stryker/Settings.java"
    click UI5 "https://github.com/stryker-defense-inc/strykerapp/tree/main/app/src/main/java/com/zalexdev/stryker/appintro"

    %% Click Events for Core Manager
    click CM "https://github.com/stryker-defense-inc/strykerapp/tree/main/app/src/main/java/com/zalexdev/stryker/coremanger"

    %% Click Events for Pentest Modules
    click PM1 "https://github.com/stryker-defense-inc/strykerapp/tree/main/app/src/main/java/com/zalexdev/stryker/exploit_hub"
    click PM2 "https://github.com/stryker-defense-inc/strykerapp/tree/main/app/src/main/java/com/zalexdev/stryker/metasploit"
    click PM3 "https://github.com/stryker-defense-inc/strykerapp/tree/main/app/src/main/java/com/zalexdev/stryker/local_network"
    click PM4 "https://github.com/stryker-defense-inc/strykerapp/tree/main/app/src/main/java/com/zalexdev/stryker/nmap"
    click PM5 "https://github.com/stryker-defense-inc/strykerapp/tree/main/app/src/main/java/com/zalexdev/stryker/router_scan"
    click PM6 "https://github.com/stryker-defense-inc/strykerapp/tree/main/app/src/main/java/com/zalexdev/stryker/searchsploit"
    click PM7 "https://github.com/stryker-defense-inc/strykerapp/tree/main/app/src/main/java/com/zalexdev/stryker/three_wifi"
    click PM8 "https://github.com/stryker-defense-inc/strykerapp/tree/main/app/src/main/java/com/zalexdev/stryker/wifi"

    %% Click Event for Assets
    click AT "https://github.com/stryker-defense-inc/strykerapp/tree/main/app/src/main/assets"

    %% Click Events for Underlying Android Infrastructure
    click IR1 "https://github.com/stryker-defense-inc/strykerapp/blob/main/app/src/main/AndroidManifest.xml"
    click IR2 "https://github.com/stryker-defense-inc/strykerapp/blob/main/app/build.gradle"

    %% Styles
    classDef ui fill:#e1f5fe,stroke:#0277bd,stroke-width:2px;
    classDef core fill:#fff9c4,stroke:#f57f17,stroke-width:2px;
    classDef module fill:#c8e6c9,stroke:#2e7d32,stroke-width:2px;
    classDef asset fill:#ffcc80,stroke:#ef6c00,stroke-width:2px;
    classDef infra fill:#d1c4e9,stroke:#512da8,stroke-width:2px;

    class UI1,UI2,UI3,UI4,UI5 ui;
    class CM core;
    class PM1,PM2,PM3,PM4,PM5,PM6,PM7,PM8 module;
    class AT asset;
    class IR1,IR2 infra;
```
