Detection of Hooking

Technique Detected:  Hooking | T1617

ID: DET0719
Domains: Mobile
Analytics: AN1850
Version: 1.0
Created: 21 October 2025
Last Modified: 12 May 2026

Analytics

AN1850

For Android, detect Hooking from documented management, network, or vetting evidence; treat state queries as periodic observations rather than real-time events. Correlate Application Permission via Android Enterprise DPC / Application Vetting [DevicePolicyManager.getPermissionGrantState(); PackageManager manifest/requested-permission review]; OS API Execution via Application Vetting / Instrumented Dynamic Analysis [Dynamic API/runtime trace: App process loads external code module or native library from non-system path injected into zygote or app_process runtime — abnormal library injection path is the hooking mechanism indicator]. Alert on a sequence or state change inconsistent with the device/app baseline, approved management policy, or expected user workflow; do not infer unobserved API calls, file/process activity, or payload content from management state alone.

Log Sources
Data Component Name Channel
Application Permission (DC0114) android:DevicePolicyManager DevicePolicyManager.getPermissionGrantState(); PackageManager manifest/requested-permission review
OS API Execution (DC0021) mobile:DynamicAnalysis Dynamic API/runtime trace: App process loads external code module or native library from non-system path injected into zygote or app_process runtime — abnormal library injection path is the hooking mechanism indicator
Mutable Elements
Field Description
RootStatusChangeWindow Default 3600s — hooking framework deployment may lag root acquisition. Root detection is the gate; hooking evidence narrows within the window.