How incrediblehacker/insta-hack works
Project type and purpose
• This is an open-source, CLI-based Instagram “hacking” toolkit packaged as a collection of Python modules and Bash scripts.
• It provides three main functions: information gathering, brute-force password attacks, and automatic account reporting.
File structure
• Top-level orchestrator scripts:
• insta-hack.sh, setup.sh, update.sh, remove.sh
These serve as the single-command entry points.
• Submodule directories:
• Ig_information_gathering/
– Core_files/Ig_information_gathering.py (main info-gathering engine)
– Core_files/PersonalLib/ (helper library modules: Fast.py, More.py, Shadow.py)
– Core_files/Users/ (local storage for output)
– start.sh, update.sh, remove.sh (module-specific scripts)
• ig_brute_force/
– core/patch.sh, core/update.sh (maintenance scripts)
– main/auto.sh, main/manual.sh (two brute-force modes)
– pass/ (wordlist files)
– ighack.sh (entrypoint for brute force)
• Configuration and dependency files:
• requirements.txt (Python dependencies)
• LICENSE, README.md
README for additional insights
• Describes the three features and supported environments (Termux, Kali).
• Shows that orchestration is via Bash wrappers around Python cores.
• No built-in web service or database—data is fetched directly over HTTP and stored in flat files.
a. Main components
• CLI Entrypoint Layer
– insta-hack.sh (top-level dispatcher)
– setup.sh / update.sh / remove.sh (lifecycle scripts)
• Functional Modules
– Info-Gathering Module
· Ig_information_gathering.py
· PersonalLib (Fast, More, Shadow)
· Users folder (local result store)
– Brute-Force Module
· ighack.sh → auto.sh & manual.sh
· Wordlists in pass/
– Auto-Reporter Module (could be in same or separate shell script)
• External Services
– Instagram HTTP endpoints (API or web scraping)
• Local Resources
– Filesystem (Users/, pass/wordlists)
– Python virtual environment & installed packages
b. Relationships and interactions
• Top-level CLI calls the appropriate sub-script (info, brute, report).
• Sub-script loads or calls Python core functions.
• Python core uses PersonalLib helpers to process data.
• All modules send HTTP requests to Instagram and parse responses.
• Results are persisted to local folders.
• update.sh scripts pull new code from GitHub; remove.sh cleans up files.
c. Architectural patterns
• Modular CLI orchestration: Bash scripts wrap Python modules.
• Separation of concerns:
– Shell layer (deployment, invocation, updates)
– Python layer (business logic for attacks)
• File-based storage: no database, simple result caching.
d. Key technologies
• Bash scripting (orchestration, installation, updates)
• Python 3 modules for HTTP requests, parsing
• Flat-file wordlists for brute-force
• GitHub for distribution/updating