How 1n3/brutex works
Project type and purpose
• BruteX is an open-source, CLI-driven security tool that automates brute-forcing of all exposed services on a target host or network.
• It ships as a single script/executable (brutex), uses local wordlists, writes out “loot,” and can be packaged in Docker or installed via install.sh.
File structure
• Top-level files:
• brutex (the main script/entrypoint)
• install.sh (installer)
• Dockerfile (container build)
• brutex.desktop (desktop launcher metadata, optional GUI integration)
• CHANGELOG.md, README.md (documentation)
• Directories:
• loot/ – where successful credentials and results are stored
• wordlists/ – a large collection of service-specific username/password lists
• No separate “backend” or “frontend”—it’s a modular CLI tool, with each service handler embedded or loaded by the main script.
Extract architecture hints from the README
• Single entrypoint: brutex target <port>
• Support for Docker: isolate runtime in a container
• License constraints: branding must remain intact
A. User Interface (CLI)
• Component: brutex script/executable
• Responsibility: accepts target and port(s), orchestrates scanning & brute-force
B. Scanner/Orchestrator
• Module inside brutex that invokes port scanning (e.g., nmap or built-in checks)
• Determines which services are alive on each port
C. Service Brute-Force Plugins
• Sub-components: FTP, SSH, MySQL, MSSQL, PostgreSQL, SMB, SNMP, etc.
• Each plugin uses its own wordlists (pulled from wordlists/) and protocol logic
D. Wordlist Data Store
• Location: wordlists/ directory
• Contains: default username/password pairs, weak/medium/hybrid lists
E. Loot Storage
• Location: loot/ directory
• Stores: per-service subfolders or files containing successful creds
F. Environment/Packaging
• install.sh installs dependencies and places brutex in PATH
• Dockerfile builds a container image bundling all scripts & wordlists
Relationships & data flows
2. CLI calls Scanner module → scans target → returns list of open ports/services
3. For each service: CLI calls corresponding Brute-Force Plugin
4. Plugin reads appropriate wordlists from the Wordlist Data Store
5. Plugin attempts logins against target service
6. On success, Plugin writes credentials to Loot Storage
7. CLI aggregates results and prints summary to console
8. Optional: user may read files under loot/ for raw output
Important architectural patterns & design principles
• Modular plugin architecture: separate brute-force logic per service
• Data-driven design: behavior determined by external wordlists
• Single responsibility: each component (scanner, orchestrator, plugin, datastore) has a clear role
• Extensibility: new service modules can be added by following plugin structure
• Environmental isolation: Docker image vs. host install via install.sh
Details
• Optional packaging paths:
• Host install via install.sh → places brutex in /usr/local/bin
• Docker build/run → container boundary around modules
• If desired, show version control artifacts (e.g., GitHub) to indicate where developers push/pull