flashnuke
diff --git a/‎README.md
Lines changed: 13 additions & 2 deletions b/‎README.md
Lines changed: 13 additions & 2 deletions
diff --git a/‎apk/README.md
Lines changed: 59 additions & 26 deletions b/‎apk/README.md
Lines changed: 59 additions & 26 deletions
diff --git a/‎apk/assets/arp.arm
-292 KB b/‎apk/assets/arp.arm
-292 KB
diff --git a/‎apk/assets/arp.arm64
-626 KB b/‎apk/assets/arp.arm64
-626 KB
diff --git a/‎apk/assets/arp.x86
-469 KB b/‎apk/assets/arp.x86
-469 KB
diff --git a/‎apk/assets/arp.x86_64
-670 KB b/‎apk/assets/arp.x86_64
-670 KB
diff --git a/‎apk/assets/nra.arm
-2.33 MB b/‎apk/assets/nra.arm
-2.33 MB
diff --git a/‎apk/assets/nra.arm64
-4.25 MB b/‎apk/assets/nra.arm64
-4.25 MB
diff --git a/‎apk/assets/nra.x86
-3.23 MB b/‎apk/assets/nra.x86
-3.23 MB
diff --git a/‎apk/assets/nra.x86_64
-4.11 MB b/‎apk/assets/nra.x86_64
-4.11 MB
diff --git a/‎apk/bin/deadnet-1.0-arm64-v8a_armeabi-v7a-debug.apk
-3.27 MB b/‎apk/bin/deadnet-1.0-arm64-v8a_armeabi-v7a-debug.apk
-3.27 MB
diff --git a/‎apk/buildozer.spec
Lines changed: 2 additions & 62 deletions b/‎apk/buildozer.spec
Lines changed: 2 additions & 62 deletions
@@ -25,21 +25,32 @@ I have a separate project for that [here](https://github.com/flashnuke/wifi-deau
 If no credentials are present and you insist on using Deadnet, it's possible to run a dictionary-attack using a [wordlist](https://github.com/flashnuke/pass-generator) in combination with another tool that cracks Wifi handshakes to gain credentials first.
 
 # Android APP
-<p align="center"><img src="https://github.com/user-attachments/assets/4282d5bb-c8b0-4081-a5d8-3b33800eadaa" width="450" ></p>
+<p align="center"><img src="https://github.com/user-attachments/assets/c85eccf8-bbf8-4904-9327-9e1c2e064eea" width="450" ></p>
 
 
 An Android APP designed to run Deadnet directly on rooted devices using a simple GUI with a couple of buttons. </br>
 See [the APK section](https://github.com/flashnuke/deadnet/tree/main/apk) for more.
 
 # Requirements
+### OS
 Works on every OS. </br>
 The only difference would be in the output, which in LINUX OS would refresh the same line to log updates rather than printing new lines in other operating systems.
 
-3rd party libraries can be installed by running the following command: `pip3 install -r requirements.txt` as they are listed inside the requirements file:
+### VM
+Beware that if running from a VM, the network should be set to `Bridged`
+
+### Dependencies
+3rd party libraries can be installed by running the following command: `pip install -r requirements.txt` as they are listed inside the requirements file:
 ```python
 scapy~=2.4.5
 ```
 # Usage
+## Installation
+```bash
+git clone https://github.com/flashnuke/deadnet.git
+cd deadnet
+pip install -r requirements.txt
+```
 
 ## Poisoning ARP Cache (IPv4)
 The network interface is a mandatory param and should always be passed, for example (`eth0` is the most commonly used in kali): 
 
@@ -1,50 +1,83 @@
 # Deadnet APK
-<p align="center"><img src="https://github.com/flashnuke/deadnet/assets/59119926/fbb72f10-764c-4272-aa8c-8623f34b8ba2" width="350" ></p>
-A simple GUI that runs Deadnet directly on Android devices. </br> </br>
+<p align="center"><img src="https://github.com/user-attachments/assets/c85eccf8-bbf8-4904-9327-9e1c2e064eea" width="450" ></p>
 
-The APK is stored inside [bin](https://github.com/flashnuke/deadnet/tree/main/apk/bin) directory, but it can be built manually as well.
-</br>The code that is supposed to open network sockets and send the spoofed packets is written in C++ and compiled into native binaries that are run explicitly by the Python app.
+A simple Android app that runs Deadnet directly on Android devices. </br> </br>
+
+The APK is stored inside [bin](https://github.com/flashnuke/deadnet/tree/main/apk/bin) directory, but can be built manually as well.
+</br>The attack is written in C++ and compiled into native binaries that are run explicitly by the Python app (see the `Notes.Permissions` section for more). </br>
 
 # Requirements
-* Device must be rooted
-* Most modern devices are ARM64. The native binaries are compiled for the following machine architecture types: (ARM, ARM64, x86, x86_64), see the building section in order to compile for a different architecture type and modify the code accordingly
+* Device must be rooted.
+* Most modern devices are ARM64. The native binaries are compiled for the following machine architecture types: (ARM, ARM64, x86, x86_64), see the building section in order to compile for a different architecture type.
+
+# Usage
+* Grant permissions.
+* Use the buttons - `Start`, `Stop` and `Refresh` (to refresh the current wifi connection info).
+* In case of an error, use the `Debug Logs` button to fetch the logs, and feel free to open a new [issue](https://github.com/flashnuke/deadnet/issues) with the debug logs included.
 
+### Permissions
+* Some parts were compiled into native binaries due to a lack of permissions that restrict the Python interpreter from directly creating raw sockets, even when running as root.
+* `ACCESS_FINE_LOCATION` permission is required in order to access SSID data (i.e. wifi network name).
 
-# Building
+# Building manually
 Steps to build the app manually. </br>
 The following tools are required:
-* NDK tools
-* Buildozer and Kivy library
+* NDK tools (to build the `.cpp` binaries)
+* Buildozer (to build the APK)
+
+### Cloning the library
+```bash
+# clone the project
+git clone https://github.com/flashnuke/deadnet.git
+```
 
 ### Compiling the C++ Binaries
 The C++ binaries source code files (`src/arp.cpp` for the ARP poisoning and `src/nra.cpp` for the dead router attack) should be compiled by NDK:
 ```bash
-cd deadnet/apk
-
-$NDK_PATH/bin/aarch64-linux-android29-clang++ -static -o assets/nra.arm64 src/nra.cpp
-$NDK_PATH/bin/armv7a-linux-androideabi29-clang++ -static -o assets/nra.arm src/nra.cpp
-$NDK_PATH/bin/i686-linux-android29-clang++ -static -o assets/nra.x86 src/nra.cpp
-$NDK_PATH/bin/x86_64-linux-android29-clang++ -static -o assets/nra.x86_64 src/nra.cpp
+cd /tmp  # DO NOT CLONE NDK INTO THE PROJECT DIRECTORY! it will mess with the build process
+mkdir android-ndk && cd android-ndk
+wget https://dl.google.com/android/repository/android-ndk-r26d-linux.zip
+unzip android-ndk-r26d-linux.zip
+export NDK_PATH=$(pwd)/android-ndk-r26d # NDK_PATH example: "NDK_PATH=/tmp/my-android-toolchain"
 
-$NDK_PATH/bin/aarch64-linux-android29-clang++ -static -o assets/arp.arm64 src/arp.cpp
-$NDK_PATH/bin/armv7a-linux-androideabi29-clang++ -static -o assets/arp.arm src/arp.cpp
-$NDK_PATH/bin/i686-linux-android29-clang++ -static -o assets/arp.x86 src/arp.cpp
-$NDK_PATH/bin/x86_64-linux-android29-clang++ -static -o assets/arp.x86_64 src/arp.cpp
+# compile binaries
+cd <path_to_deadnet_root>/apk
+$NDK_PATH/toolchains/llvm/prebuilt/linux-x86_64/bin/aarch64-linux-android29-clang++ -static -o assets/nra.arm64 src/nra.cpp
+$NDK_PATH/toolchains/llvm/prebuilt/linux-x86_64/bin/armv7a-linux-androideabi29-clang++ -static -o assets/nra.arm src/nra.cpp
+$NDK_PATH/toolchains/llvm/prebuilt/linux-x86_64/bin/i686-linux-android29-clang++ -static -o assets/nra.x86 src/nra.cpp
+$NDK_PATH/toolchains/llvm/prebuilt/linux-x86_64/bin/x86_64-linux-android29-clang++ -static -o assets/nra.x86_64 src/nra.cpp
 
-# NDK_PATH example: "NDK_PATH=/home/ubuntu/my-android-toolchain"
+$NDK_PATH/toolchains/llvm/prebuilt/linux-x86_64/bin/aarch64-linux-android29-clang++ -static -o assets/arp.arm64 src/arp.cpp
+$NDK_PATH/toolchains/llvm/prebuilt/linux-x86_64/bin/armv7a-linux-androideabi29-clang++ -static -o assets/arp.arm src/arp.cpp
+$NDK_PATH/toolchains/llvm/prebuilt/linux-x86_64/bin/i686-linux-android29-clang++ -static -o assets/arp.x86 src/arp.cpp
+$NDK_PATH/toolchains/llvm/prebuilt/linux-x86_64/bin/x86_64-linux-android29-clang++ -static -o assets/arp.x86_64 src/arp.cpp
 ```
 
+The compiled binaries will be stored under `./assets`.
+
 ### Building the APK
 ```bash
-cd deadnet/apk
+# navigate to the apk directory
+cd <path_to_deadnet_root>/apk
+
+# make sure you have python 3.10 installed
+python3.10 --version
+python3.10 -m venv venv
+source venv/bin/activate
+
+# install buildozer - refer to ths official for more https://buildozer.readthedocs.io/en/latest/installation.html
+
+# build the apk 
 buildozer android debug # build in debug mode
 ```
+The compiled APK will be stored under `./bin`.
 
-# Notes
-### Permissions
-* Some parts were compiled into native binaries due to lack of permissions to open raw sockets by the Python interpreter on Android (even when root)
-* `ACCESS_FINE_LOCATION` permission is requested in order to access the SSID (wifi network name)
-
+# Debugging
+### Debug Logs
+Quick debugging can be done using the `Debug Logs` button, which will display useful logs. </br>
+### ADB logcat
+If a more thorough debug process is needed, `adb` is the right for that. </br>
+Connecting the device to ADB and running `adb logcat` would show all the logs, which can be filtered further by using `adb logcat | grep -E 'python|DeadNet'`.
 
 # Disclaimer
 
 
@@ -37,7 +37,7 @@ version = 1.0
 
 # (list) Application requirements
 # comma separated e.g. requirements = sqlite3,kivy
-requirements = python3,kivy,scapy,netifaces,ipaddress,android
+requirements = kivymd==1.2.0,kivy==2.3.0,android
 
 # (str) Custom source folders for requirements
 # Sets custom source for any requirements with recipes
@@ -56,19 +56,6 @@ orientation = portrait
 # (list) List of service to declare
 #services = NAME:ENTRYPOINT_TO_PY,NAME2:ENTRYPOINT2_TO_PY
 
-#
-# OSX Specific
-#
-
-#
-author = flashnuke
-
-# change the major version of python used by the app
-osx.python_version = 3
-
-# Kivy version to use
-osx.kivy_version = 1.9.1
-
 #
 # Android specific
 #
@@ -105,7 +92,7 @@ android.permissions = CHANGE_WIFI_STATE,READ_SECURE_SETTINGS,ACCESS_NETWORK_STAT
 android.api = 33
 
 # (int) Minimum API your APK / AAB will support.
-#android.minapi = 21
+android.minapi = 21
 
 # (int) Android SDK version to use
 #android.sdk = 20
@@ -353,53 +340,6 @@ android.allow_backup = True
 #p4a.extra_args =
 
 
-
-#
-# iOS specific
-#
-
-# (str) Path to a custom kivy-ios folder
-#ios.kivy_ios_dir = ../kivy-ios
-# Alternately, specify the URL and branch of a git checkout:
-ios.kivy_ios_url = https://github.com/kivy/kivy-ios
-ios.kivy_ios_branch = master
-
-# Another platform dependency: ios-deploy
-# Uncomment to use a custom checkout
-#ios.ios_deploy_dir = ../ios_deploy
-# Or specify URL and branch
-ios.ios_deploy_url = https://github.com/phonegap/ios-deploy
-ios.ios_deploy_branch = 1.10.0
-
-# (bool) Whether or not to sign the code
-ios.codesign.allowed = false
-
-# (str) Name of the certificate to use for signing the debug version
-# Get a list of available identities: buildozer ios list_identities
-#ios.codesign.debug = "iPhone Developer: <lastname> <firstname> (<hexstring>)"
-
-# (str) The development team to use for signing the debug version
-#ios.codesign.development_team.debug = <hexstring>
-
-# (str) Name of the certificate to use for signing the release version
-#ios.codesign.release = %(ios.codesign.debug)s
-
-# (str) The development team to use for signing the release version
-#ios.codesign.development_team.release = <hexstring>
-
-# (str) URL pointing to .ipa file to be installed
-# This option should be defined along with `display_image_url` and `full_size_image_url` options.
-#ios.manifest.app_url =
-
-# (str) URL pointing to an icon (57x57px) to be displayed during download
-# This option should be defined along with `app_url` and `full_size_image_url` options.
-#ios.manifest.display_image_url =
-
-# (str) URL pointing to a large icon (512x512px) to be used by iTunes
-# This option should be defined along with `app_url` and `display_image_url` options.
-#ios.manifest.full_size_image_url =
-
-
 [buildozer]
 
 # (int) Log level (0 = error only, 1 = info, 2 = debug (with command output))