Detection of Broadcast Receivers

Technique Detected:  Broadcast Receivers | T1624.001

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

Analytics

AN1837

For Android, detect Broadcast Receivers primarily during application vetting or controlled analysis rather than assuming a live device SOC feed. Correlate OS API Execution via Application Vetting / Instrumented Dynamic Analysis [Dynamic API/runtime trace: Application registers BroadcastReceiver via registerReceiver() or manifest-declared receiver for sensitive system intents (BOOT_COMPLETED, SMS_RECEIVED, ACTION_PACKAGE_REPLACED, CONNECTIVITY_CHANGE, USER_PRESENT) NOT IN $ApprovedReceiverApp]. 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
OS API Execution (DC0021) mobile:DynamicAnalysis Dynamic API/runtime trace: Application registers BroadcastReceiver via registerReceiver() or manifest-declared receiver for sensitive system intents (BOOT_COMPLETED, SMS_RECEIVED, ACTION_PACKAGE_REPLACED, CONNECTIVITY_CHANGE, USER_PRESENT) NOT IN $ApprovedReceiverApp
Mutable Elements
Field Description
ApprovedReceiverApps MDM agent (BOOT_COMPLETED for policy enforcement), approved enterprise apps with documented broadcast receiver need. Derive from MDM catalog.
ReceiverWindow Default 60s between broadcast receipt and follow-on activity.