Detection of Input Injection

Technique Detected:  Input Injection | T1516

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

Analytics

AN1666

For Android, detect Input Injection from documented management, network, or vetting evidence; treat state queries as periodic observations rather than real-time events. Correlate Application State via Android Enterprise / EMM [Managed package inventory/status and package metadata]; OS API Execution via Application Vetting / Instrumented Dynamic Analysis [Dynamic API/runtime trace: Accessibility-enabled app NOT IN $AccessibilityAllowList$ invokes performAction() click, global action (GLOBAL_ACTION_BACK/HOME/RECENTS), or insertText() on a UI element belonging to a different foregrounded app — cross-app UI action is the]. 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 State (DC0123) android:EMM Managed package inventory/status and package metadata
OS API Execution (DC0021) mobile:DynamicAnalysis Dynamic API/runtime trace: Accessibility-enabled app NOT IN $AccessibilityAllowList$ invokes performAction() click, global action (GLOBAL_ACTION_BACK/HOME/RECENTS), or insertText() on a UI element belonging to a different foregrounded app — cross-app UI action is the
Mutable Elements
Field Description
AccessibilityAllowList Approved assistive technology apps with legitimate UI automation need. Minimal list. Derive from MDM catalog accessibility policy.
InjectionInteractionThreshold Default 5s. UI actions occurring >5s after last detected user touch without expected foreground transition are injection-driven. Tightening: 2s.
TargetAppList Banking, enterprise SSO, authentication, payment app packages. Injections against these raise confidence from Medium to High.