How xdeadhackerx/the_cracker works
Project Type and Purpose
• This is a command-line security assessment tool (bash script) called “The_Cracker.”
• Its purpose is to automate brute-force and dictionary attacks against various targets: encrypted files (Office, PDF, ZIP, RAR), network protocols (FTP, SSH, Telnet, SMB, RDP), captured Wi-Fi handshakes and generic hashes, local IP logins, plus dictionary generation and hash utilities.
File Structure Analysis
• Top‐level files:
• LICENSE, README.md
• the_cracker.sh – the single entry-point shell script providing a menu-driven CLI
• requisitos/0.sh – requisitos/1.sh … requisitos/5.sh – installer & dependency checker scripts
• The directory requisitos likely also contains subdirectories for results (e.g., requisitos/resultados/dicc.txt) as noted in the README.
• No separate “src” or “lib” folders; all functionality is orchestrated by the_cracker.sh, calling out to dependencies and installer scripts.
Key Components
a. User Interface Layer
• the_cracker.sh – main menu, user input, control flow
b. Installer & Dependency Manager
• requisitos/0.sh … requisitos/5.sh – check/install required external tools (hashcat, john, hydra, nmap, zip2john, rar2john, pdfcrack, fcrackzip, hash-identifier, etc.)
c. Functional Modules
• File Decryption Module – brute-force & dictionary attacks on Office/PDF/ZIP/RAR
• Network Protocol Attack Module – dictionary attacks via Hydra/ncrack against FTP/SSH/Telnet/SMB/RDP; includes optional nmap scan
• Handshake/Hash Cracking Module – uses hashcat/john to crack Wi-Fi handshakes and generic hashes
• Local Login Module – network scan + dictionary attack on a specific IP:port
• Dictionary Creation Module – user-driven wordlist builder (names, dates, pets, custom patterns)
• Utilities Module – hash extraction from .cap, hash-type identification, hash generation
d. External Tools & Services
• Hydra, ncrack, nmap, hashcat, John the Ripper, pdfcrack, fcrackzip, zip2john, rar2john, hash-identifier
Relationships and Data Flow
• User → the_cracker.sh (CLI commands)
• the_cracker.sh → requisitos/*.sh (dependency installation/verification)
• the_cracker.sh → Functional Modules
• Each Functional Module → External Tools (e.g., File Decryption Module → fcrackzip/pdfcrack/zip2john)
• Network Modules → Network (target IP:port)
• Handshake Module → File System (input .cap → output hash)
• Dictionary Creation Module → File System (output wordlist)
• Utilities Module ↔ File System (read/write hashes, identify types)
Architectural Patterns and Principles
• Single Orchestrator Pattern: one script controls all workflows
• Modular Design: discrete modules for each attack vector and utility
• Externalization of Dependencies: uses separate installer scripts (requisitos) to decouple tool installation from core logic
• CLI-Driven Workflow: linear, menu-based control flow
Elements
• Notes on protocol/attack type next to network-facing modules