Threadlinqs IntelligenceStart free

ATT&CK techniquePersistence (Mobile)

T1624 Event Triggered Execution

Persistence (Mobile)Mobile

As of 2026-11-19, T1624 (Event Triggered Execution) appears in 19 tracked threats, first reported 2026-03-07 and most recently 2026-08-05, with linked actors including EVLF; it most often appears alongside T1417 (Input Capture).

Tracked threats
192 critical, 14 high, 2 medium, 1 low
First seen
2026-03-07
Last seen
2026-08-05
Threat actors
1In the threats using it
Detection rules
19Unlock with TL Creds

Data as of:

Activity timeline

T1624 first appeared in tracked threats on and was most recently reported on . The busiest month was 2026-07 with 12 reports, and 19 of the 19 threats were reported in the twelve months to 2026-08.

How adversaries use it

T1624 Event Triggered Execution is catalogued by MITRE ATT&CK under the Persistence (Mobile) tactic in the Mobile matrix. Threadlinqs maps 19 of 4091 tracked threats (0.5%) to it; by severity that is 2 critical, 14 high, 2 medium, 1 low.

Threats that use T1624 most often also use T1417 Input Capture (17 threats), T1437 Application Layer Protocol (17 threats), T1426 System Information Discovery (14 threats), T1646 Exfiltration Over C2 Channel (14 threats), T1660 Phishing (14 threats). These are the techniques an intrusion set tends to chain with it, so they are the natural next places to look when it is observed.

1 tracked threat actor appear in the threats that use T1624; the most frequent are EVLF (1).

Mitigations

MITRE ATT&CK lists 1 mitigation for T1624.

Threat actors using it

Tracked threats

19 tracked threats use T1624.

Detection coverage

Threadlinqs maintains 19 detection rules mapped to T1624 (SPL 6, KQL 5, Sigma 8). Rule content unlocks with TL Creds on a free account; this page shows counts only.

19 detection rules (SPL/KQL/Sigma) · unlock with TL Creds. Sign up free to unlock the detection rules or query them with the Threadlinqs MCP server (Purple)

Sub-techniques