Skip to content
github-actions[bot] edited this page Nov 19, 2026 · 4 revisions

Mobile penetration testing, device security, forensics, and authorized attack platforms

Part of the ULTIMATE CYBERSECURITY MASTER GUIDE

NetHunter Android iOS


Other mobile security references: Android Security, OSX and iOS Security, and curated source map.

Linux-on-Android companion: UserLAnd Setup & Operations explains userspace Linux on Android, scope and platform limitations.

Forensic triage companion: MVT mobile verification workflow addresses owner consent, iOS/Android backup/artifact limitations and uncertainty; it does not guarantee spyware detection.

๐ŸŽฏ Purpose

Mobile security reference covering device preparation (rooting, custom ROM), mobile pentesting platforms (Kali NetHunter), Android/iOS app security assessment, mobile forensics, and device OSINT. Currently focused on the OnePlus 6 A6003 as the primary NetHunter attack platform.

โš™๏ธ Function

Covers: OnePlus 6 rooting workflow (bootloader unlock, LineageOS, TWRP, Magisk), Kali NetHunter install and configuration, field SOPs for NetHunter attack modules (HID, BadUSB, WifiPumpkin, Bluetooth Arsenal, Wardriving), Android APK assessment, iOS backup forensics, and mobile device OSINT tools.

๐Ÿ† Goal

Enable practitioners to build and operate a capable mobile pentesting platform (NetHunter on OnePlus 6), conduct authorized Android and iOS app assessments, and perform forensic or OSINT tasks against mobile devices.

๐Ÿ“‹ When To Use

  • Setting up or maintaining the OnePlus 6 NetHunter device
  • Running a NetHunter-based engagement (HID, Evil AP, Wardriving, etc.)
  • Conducting an authorized Android or iOS app penetration test
  • Performing iOS backup forensics or mobile device OSINT

๐Ÿ“‹ Table Of Contents


๐ŸŽฏ Overview

Mobile device application identity and cloud security layers

Mobile device security varies by OS model and account backup settings.

This directory contains mobile security resources for penetration testers, forensic investigators, and security researchers - from device preparation and platform setup through offensive tooling, app security assessment, and forensic analysis.

What You'll Find Here:

  • ๐Ÿ“ฑ OnePlus 6 rooting and custom ROM installation guides
  • ๐Ÿ‰ Kali NetHunter setup, configuration, and field SOPs
  • ๐Ÿค– Android application security assessment checklists
  • ๐ŸŽ iOS backup forensics scripts
  • ๐Ÿ“ก Mobile device OSINT tools (WiFi/Bluetooth enumeration)
  • ๐Ÿ”ง Mobile pentesting toolchain reference (MobSF, Frida, Objection, APKTool)
  • ๐Ÿ“‹ Assessment methodology for Android and iOS apps (OWASP MASTG-aligned)

๐Ÿ“‚ Current Content

Engagement Sops

File Description Status
mobile_pentest_sop.md Full engagement-level SOP for pentesting with the NetHunter device: pre-engagement legal/device prep, passive recon, active recon, exploitation (Evil AP, HID, BadUSB, LLMNR, Metasploit), post-exploitation, evidence handling, teardown, and report structure โœ… Complete
Nethunter_SOP.md Field SOPs for operating all Kali NetHunter attack modules and utilities on the OnePlus 6 during authorized penetration tests. From pre-engagement setup through post-engagement teardown and evidence handling. โœ… Complete

Oneplus 6 / Kali Nethunter (Device-specific)

File Description Status
OnePlus_A6003/Rooting.md Phase-by-phase: bootloader unlock, dtbo flash, LineageOS 22.2 install via sideload, TWRP install (temporary-boot method), and Magisk root via boot image patching โœ… Complete
OnePlus_A6003/Kali_NetHunter.md NetHunter install (Magisk module or TWRP), LineageOS prerequisite, post-install config, metapackage and app selection, chroot management โœ… Complete
OnePlus_A6003/Nethunter_SOP.md Per-module SOPs for all NetHunter tools: HID, DuckHunter, BadUSB, WifiPumpkin, WPS attacks, Bluetooth Arsenal, Wardriving, SET, Nmap, Metasploit, KeX, MAC changer, CARsenal, teardown checklist โœ… Complete

Checklists

File Description Status
Checklists/Android-Applications-Checklist.md 8-item Android APK triage: manifest review, WebView, certificate pinning, rooting detection, obfuscation, payload injection. OWASP MASTG-aligned. โœ… Complete

Scripts

File Description Status
Scripts/Python/iphone_messages.py Extract SMS/iMessage content from an iOS backup directory (SQLite-based) โœ… Complete
Scripts/Python/iphone_finder.py Detect nearby iPhones via WiFi OUI sniffing and Bluetooth MAC derivation using Scapy โœ… Complete

๐Ÿ—บ๏ธ Mobile Pentesting Toolchain

Android

Tool Purpose Install
MobSF Automated static + dynamic analysis framework docker run -it -p 8000:8000 opensecurity/mobile-security-framework-mobsf
APKTool Decompile/recompile APKs sudo apt install apktool
jadx APK to Java source decompiler sudo apt install jadx
Frida Dynamic instrumentation toolkit pip install frida-tools
Objection Runtime mobile exploration (Frida-based) pip install objection
Drozer Android attack surface analyzer pip install drozer
Burp Suite HTTP/HTTPS proxy for authorized testing Android user-CA trust depends on target SDK and Network Security Configuration: API 24+ defaults to system CAs, while API 23 and lower also trust user-added CAs by default. Custom trust or pinning may still reject the proxy.
apksigner Sign repackaged APKs Included in Android SDK build-tools

iOS

Tool Purpose Notes
libimobiledevice Interact with iOS devices over USB sudo apt install libimobiledevice-utils
idevicebackup2 Create/restore iOS backups Part of libimobiledevice
Frida on iOS Dynamic instrumentation (requires jailbreak or sideload) Works with checkra1n/palera1n
Burp Suite on iOS HTTPS proxy for authorized testing A manually installed CA profile must be enabled under Settings โ†’ General โ†’ About โ†’ Certificate Trust Settings for SSL/TLS; app-specific trust or pinning may still reject it.
SSL Kill Switch 2 Legacy iOS jailbreak test tweak Compatibility varies by iOS and app trust implementation; it does not guarantee interception of every app.

๐Ÿ“Š Mobile HTTPS Proxy Trust Flow

Use a controlled test device and authorized application. Installing a proxy CA is only one trust step; platform defaults and app-specific trust policy determine whether HTTPS traffic can be inspected.

Conceptual Android and iOS HTTPS proxy flow showing CA installation, platform and app trust checks, possible pinning rejection, and validation against a test endpoint

Conceptual comparison. Android trust depends on the app's target SDK and network security configuration. Manually installed iOS certificate profiles require full trust to be enabled for SSL/TLS. App pinning or custom trust can still reject the proxy.

References: Android Network Security Configuration ยท Apple certificate trust for manually installed profiles ยท Burp mobile configuration

๐Ÿ”ฌ Testing Methodology Overview

Android App Assessment (OWASP Mastg Order)

1. Reconnaissance
   - Download APK (APK Mirror, Google Play via gplaydl, direct from device)
   - Identify app version, permissions, target SDK

2. Static Analysis
   - apktool d target.apk          # Decompile resources + smali
   - jadx -d output/ target.apk    # Java source decompile
   - Review AndroidManifest.xml    # Permissions, exported components, debuggable flag
   - grep -r "http://" ./          # Plaintext URLs
   - grep -r "api_key\|secret\|password" ./  # Hardcoded secrets

3. Dynamic Analysis (rooted device or emulator)
   - adb install target.apk
   - objection -g com.target.app explore
   - Review target SDK and Network Security Configuration; use an approved test/debug build for trust-policy testing rather than assuming a user CA will be accepted.
   - objection > android hooking list classes

4. Network Traffic
   - Configure Burp Suite proxy on device
   - Install Burp CA certificate
   - Validate the proxy with a known test endpoint; record which requests are visible and whether app-specific trust or pinning rejects interception.
   - Intercept or modify traffic only within the written assessment scope.

5. Report
   - Map findings to OWASP MASVS controls
   - Provide PoC screenshots/Burp captures

iOS App Assessment (OWASP Mastg Order)

1. Reconnaissance
   - Obtain IPA (from device with ipainstaller, from developer, or via Frida dump)
   - unzip target.ipa && cd Payload/target.app

2. Static Analysis
   - otool -L target_binary        # Linked frameworks
   - strings target_binary | grep -i "key\|secret\|api\|http"
   - class-dump target_binary      # Objective-C class headers
   - Check Info.plist: NSAppTransportSecurity, permissions

3. Dynamic Analysis (jailbroken device)
   - objection -g com.target.app explore
   - Review the app's trust behavior in an authorized test build; instrumentation and network capture results vary by iOS and app implementation.
   - objection > ios hooking list classes

4. Network Traffic
   - Configure the proxy on the controlled test device/network.
   - Install the test CA profile; for a manually installed profile, enable full trust in Settings -> General -> About -> Certificate Trust Settings.
   - Validate with a known test endpoint. App-specific trust or pinning may still reject interception; document the limit and use an approved test build for policy testing.
   - Remove the test CA and proxy settings when testing is complete.

5. Report
   - Map to OWASP MASVS controls

๐Ÿ“‹ Suggested Future Content

The following files would round out this section:

High Priority

File Content
Mobile/android_pentest.md Full Android assessment guide: APKTool workflow, Frida/Objection cheat sheet, Drozer module commands, Burp + Android proxy setup, emulator setup (AVD + root), common vulnerability PoCs (exported activities, content providers, deeplinks)
Mobile/ios_pentest.md Full iOS assessment guide: IPA extraction, class-dump, Frida on iOS, SSL pinning bypass techniques, Keychain dumping, jailbreak options (palera1n, checkra1n)
Mobile/mobile_forensics.md iOS and Android forensics: iOS backup structure and key SQLite files (SMS, call history, locations, app data), Android ADB extraction, timeline reconstruction

Medium Priority

File Content
Mobile/mobile_opsec.md Mobile OPSEC: GrapheneOS/CalyxOS for operational security, airplane mode vs. Faraday bag, location data risks (cell towers, WiFi geolocation, Bluetooth), Signal configuration
Mobile/mdm_security.md MDM security: enrollment bypass, profile inspection, MDM command interception, detecting over-privileged MDM profiles
Mobile/mobile_malware.md Mobile malware analysis: Android APK static workflow, common families (banking trojans, stalkerware), deobfuscation of packed APKs

Lower Priority / Future

File Content
Mobile/bluetooth_attacks.md Bluetooth attack reference: BLE sniffing (Wireshark + nRF52840), BLUFFS/BIAS/KNOB attacks, BLE GATT enumeration with gatttool/gattacker
Mobile/android_checklist_extended.md Extended Android checklist: full OWASP MASTG test cases organized by MASVS category (MASVS-STORAGE, MASVS-NETWORK, MASVS-AUTH, MASVS-CODE, MASVS-RESILIENCE)

๐Ÿค Contributing

To contribute to the Mobile section:

  1. Follow the 4-header standard: ## ๐ŸŽฏ Purpose, ## โš™๏ธ Function, ## ๐Ÿ† Goal, ## ๐Ÿ“‹ When to Use after every H1
  2. Add a ## Related Files section at the bottom with bidirectional links
  3. Use hyphens (-) not em-dashes
  4. Verify all commands against the current tool version before adding
  5. Include written authorization reminders for any offensive technique
  6. For device-specific guides, note the exact firmware/OS version tested against

๐Ÿ“š Resources

Official Documentation

Mobile Pentesting Tools

  • MobSF - Mobile Security Framework
  • Frida - Dynamic instrumentation toolkit
  • Objection - Runtime mobile exploration
  • APKTool - APK reverse engineering
  • jadx - Java decompiler for APKs
  • Drozer - Android attack surface analyzer

Learning Resources


Related Files


โš ๏ธ Security & Legal Disclaimer

๐Ÿ”ด Critical: Authorized Use Only

โš ๏ธ LEGAL AND ETHICAL USE ONLY โš ๏ธ

This section contains attack techniques and tools for:

โœ… AUTHORIZED USES:
   - Penetration testing with explicit written authorization
   - Mobile device security assessments with client permission
   - Red team operations with organizational approval
   - Forensic investigations with proper legal authority
   - Security research in isolated lab environments
   - Blue team training and detection development
   - CTF competitions and authorized challenges
   - Educational purposes with proper supervision

๐Ÿšซ STRICTLY PROHIBITED:
   - Attacking devices, apps, or networks without explicit written permission
   - Intercepting wireless communications without authorization
   - Installing unauthorized software on devices you don't own
   - Exceeding authorized scope of engagement
   - Using attack techniques for malicious purposes
   - Any illegal or unethical activities

Legal Requirements For Mobile Security Testing

Written Authorization Requirements

CRITICAL: ALWAYS obtain written authorization that explicitly includes:

  • Specific devices, apps, networks, and SSIDs in scope
  • Testing methodology and techniques approved
  • Time windows for testing activities
  • Out-of-scope systems and explicit restrictions
  • Emergency contact information and escalation procedures
  • Data handling and confidentiality requirements
  • Physical access authorization if HID/BadUSB is in scope
  • RF activity authorization if Evil AP or deauth attacks are in scope

Applicable Laws

Mobile security testing intersects multiple legal frameworks:

  • Computer Fraud and Abuse Act (CFAA) - unauthorized access to computers and networks
  • Electronic Communications Privacy Act (ECPA) - interception of wireless communications
  • FCC Regulations - RF transmissions and interference with licensed spectrum
  • State/Local Laws - vary by jurisdiction; some states have stricter computer crime laws
  • International Laws - GDPR (EU), Computer Misuse Act (UK), and equivalents apply when testing crosses borders
โœ… IN SCOPE (With Explicit Authorization):
   - Devices and apps explicitly listed in engagement letter
   - Networks and SSIDs defined in written agreement
   - Specific techniques approved by client/device owner
   - Testing within authorized time windows

๐Ÿšซ OUT OF SCOPE (Always):
   - Devices or networks not explicitly in scope
   - Production systems without change-window approval
   - RF attacks that could disrupt safety-critical systems
   - Any technique that could affect bystander devices

๐Ÿ“– Use These Resources Responsibly: Authorization is MANDATORY

Attack techniques are powerful - use them ethically and legally.

Repository: ULTIMATE CYBERSECURITY MASTER GUIDE

Maintained by: Pacific Northwest Computers


โš ๏ธ CRITICAL: These are ATTACK TECHNIQUES - Written authorization is REQUIRED โš ๏ธ

โš ๏ธ Unauthorized use is a FEDERAL CRIME with up to 10 years imprisonment โš ๏ธ

โš ๏ธ ALWAYS obtain explicit written authorization before using any technique โš ๏ธ

โญ Star this repo if you find it useful! โญ


๐Ÿ“‘ All Pages in Mobile

Guides & Reference

One Plus A6003

User LAnd


๐Ÿ“‚ Folder: Mobile | โœ๏ธ Suggest an edit | ๐Ÿ—บ๏ธ Browse by Topic

Clone this wiki locally