How stryker-defense-inc/strykerapp works
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).