cti-ATT-CK-v13.1/mobile-attack/attack-pattern/attack-pattern--3775a580-a1d1-46c4-8147-c614a715f2e9.json

{
    "type": "bundle",
    "id": "bundle--30e2a6c9-a3c5-429c-aaa8-edc6e64af1ff",
    "spec_version": "2.0",
    "objects": [
        {
            "modified": "2023-03-16T18:27:42.752Z",
            "name": "Broadcast Receivers",
            "description": "Adversaries may establish persistence using system mechanisms that trigger execution based on specific events. Mobile operating systems have means to subscribe to events such as receiving an SMS message, device boot completion, or other device activities. \n\nAn intent is a message passed between Android applications or system components. Applications can register to receive broadcast intents at runtime, which are system-wide intents delivered to each app when certain events happen on the device, such as network changes or the user unlocking the screen. Malicious applications can then trigger certain actions within the app based on which broadcast intent was received. \n\nIn addition to Android system intents, malicious applications can register for intents broadcasted by other applications. This allows the malware to respond based on actions in other applications. This behavior typically indicates a more intimate knowledge, or potentially the targeting of specific devices, users, or applications. \n\nIn Android 8 (API level 26), broadcast intent behavior was changed, limiting the implicit intents that applications can register for in the manifest. In most cases, applications that register through the manifest will no longer receive the broadcasts. Now, applications must register context-specific broadcast receivers while the user is actively using the app.(Citation: Android Changes to System Broadcasts) ",
            "kill_chain_phases": [
                {
                    "kill_chain_name": "mitre-mobile-attack",
                    "phase_name": "persistence"
                }
            ],
            "x_mitre_contributors": [
                "Alex Hinchliffe, Palo Alto Networks"
            ],
            "x_mitre_deprecated": false,
            "x_mitre_detection": "Application vetting services can detect which broadcast intents an application registers for and which permissions it requests. ",
            "x_mitre_domains": [
                "mobile-attack"
            ],
            "x_mitre_is_subtechnique": true,
            "x_mitre_platforms": [
                "Android"
            ],
            "x_mitre_version": "1.1",
            "x_mitre_tactic_type": [
                "Post-Adversary Device Access"
            ],
            "type": "attack-pattern",
            "id": "attack-pattern--3775a580-a1d1-46c4-8147-c614a715f2e9",
            "created": "2022-03-30T14:41:00.672Z",
            "created_by_ref": "identity--c78cb6e5-0c4b-4611-8297-d1b8b55e40b5",
            "revoked": false,
            "external_references": [
                {
                    "source_name": "mitre-attack",
                    "url": "https://attack.mitre.org/techniques/T1624/001",
                    "external_id": "T1624.001"
                },
                {
                    "source_name": "Android Changes to System Broadcasts",
                    "description": "Google. (2019, December 27). Broadcasts Overview. Retrieved January 27, 2020.",
                    "url": "https://developer.android.com/guide/components/broadcasts#changes-system-broadcasts"
                }
            ],
            "object_marking_refs": [
                "marking-definition--fa42a846-8d90-4e51-bc29-71d5b4802168"
            ],
            "x_mitre_attack_spec_version": "3.1.0",
            "x_mitre_modified_by_ref": "identity--c78cb6e5-0c4b-4611-8297-d1b8b55e40b5"
        }
    ]
}