How hack-bitgod/whatsapphacking works
Project Type and Purpose
• This is a command‐line driven Android “builder” tool whose goal is to (a) generate a specially crafted WhatsApp message to crash the official client, and (b) repackage/install a malicious WhatsApp APK containing a payload that extracts media files.
• It combines shell scripts, a Python helper, a Gradle-based Android app, raw smali payload code, auxiliary Java libraries, and signing keystores.
High‐Level File‐Structure Analysis
• Top level:
• whatsapphack.sh & hack.py – the orchestrating scripts.
• cleanup.sh – resets any temporary artifacts.
• data/ – a Gradle Android project (“app”) plus wrapper configs.
• payload/ – decompiled APK smali code with a Metasploit stage.
• java/classes/ – helper Java bytecode utilities (e.g., obfuscator).
• lib/aso.jar – third-party libraries.
• signingg.keystore & key.keystore – keys for APK signing.
• WhatsApp_files/ – CSS/JS snippets for the crash text delivery.
• Patterns:
• Builder pipeline: scripts → payload injection → Gradle build → sign → output APK.
• Modular separation: Android source (data/app), raw smali stage (payload/), utility code (java/classes, lib/).
Key README Insights
• Describes prerequisites (Java JDK, Gradle, Android Studio).
• Explains execution steps: clone repo, run whatsapphack.sh, optionally run crash via Python.
Detailed Capture of Essential Elements
• Signing keystore feeding into the final artifact node.
• A loop from cleanup.sh back to build modules for iterative runs.