T1516 Input Injection — Attack Simulation

DC0123 collection page — Instrument the owned app lifecycle and corroborate permitted service snapshots; distinguish app events from inferred gateway activity.

Providers and collection configuration

• Android logcat: Permitted logs from a consented test device/emulator; output depends on build, permissions and instrumentation.
• Android dumpsys: Point-in-time service/package state on an authorized development device.
• Instrumented test application: Own-app permission, API and state callbacks; not universal visibility into other apps.

• Use a disposable emulator or owned development device with approved debugging. Record OS/API level, app version and instrumentation privileges.
• Collect only relevant logcat buffers/tags and service snapshots; add explicit own-app instrumentation for events absent from OS logs.
• Forward sanitized logs and compare before/after state. Remove test data and revoke debugging access after the lab session.

Required normalized fields: package, state_before, state_after, source.

Illustrative collection event

Project-normalized synthetic JSON, not a native provider log, captured event, attack verdict or validated detection. A parser/adapter is required for a real SIEM. Example names, IPs and values are fictional.

{
  "schema": "1200km.telemetry.example.v1",
  "synthetic": true,
  "timestamp": "2026-09-27T12:00:00Z",
  "telemetry_id": "DC0123",
  "collector": "illustrative-lab-collector",
  "observation": {
    "package": "test.example.lab",
    "state_before": "background",
    "state_after": "foreground",
    "source": "own_app_callback"
  }
}

Visibility limits: Android tooling does not imply iOS coverage. Standard mobile apps cannot observe all other apps or protected OS internals; MDM status is not full API, filesystem or content telemetry.

DC0021 collection page — Use an approved EDR trace or instrument the owned lab process at selected APIs. Define API name, caller, sanitized arguments and return status.

Providers and collection configuration

• Application audit logs: First-party service events and request/result fields; schema is application-specific.
• OpenTelemetry-compatible log pipelines: Transport and normalization of emitted records; do not create missing audit instrumentation.

• Enable the application audit category or instrument the owned lab application at the authorization/action boundary.
• Define a schema with timestamp, service, actor, object, action, result and correlation ID. Export structured records through an authenticated collector.
• Redact secrets and personal content, separate audit from debug logs, set retention and verify delivery during rotation/restart.

Required normalized fields: process_id, api, path, result.

Illustrative collection event

Project-normalized synthetic JSON, not a native provider log, captured event, attack verdict or validated detection. A parser/adapter is required for a real SIEM. Example names, IPs and values are fictional.

{
  "schema": "1200km.telemetry.example.v1",
  "synthetic": true,
  "timestamp": "2026-09-27T12:00:00Z",
  "telemetry_id": "DC0021",
  "collector": "illustrative-lab-collector",
  "observation": {
    "process_id": 4200,
    "api": "CreateFileW",
    "path": "C:\\Lab\\demo.txt",
    "result": "success"
  }
}

Visibility limits: Debug output is not necessarily a durable audit trail. Application developers must emit the relevant event; installing a log pipeline does not make an absent event exist.

MITRE detection strategy

No exact-tagged Sigma source rule was imported. This does not establish that the technique is undetectable; the MITRE guidance and collection requirements remain relevant.

• S0403 Riltok — malware.

  Riltok injects input to set itself as the default SMS handler by clicking the appropriate places on the screen. It can also close or minimize targeted antivirus applications and the device security settings screen.[Kaspersky Riltok June 2019]

  Exact relationship: relationship--e9607e4f-5743-4bbb-b7d4-5554d66c8be7
• S0406 Gustuff — malware.

  Gustuff injects the global action `GLOBAL_ACTION_BACK` to mimic pressing the back button to close the application if a call to an open antivirus application is detected.[Talos Gustuff Apr 2019]

  Exact relationship: relationship--cacc0b72-9d73-4381-90e9-545ba908722c
• S0423 Ginp — malware.

  Ginp can inject input to make itself the default SMS handler.[ThreatFabric Ginp]

  Exact relationship: relationship--43a62244-29f1-4f7f-bc9f-9b7b8e488b38
• S0427 TrickMo — malware.

  TrickMo can inject input to set itself as the default SMS handler, and to automatically click through pop-ups without giving the user any time to react.[SecurityIntelligence TrickMo]

  Exact relationship: relationship--740ea19e-d248-44e5-a0e5-3e9420df9dc8
• S0479 DEFENSOR ID — malware.

  DEFENSOR ID can abuse the accessibility service to perform actions on behalf of the user, including launching attacker-specified applications to steal data.[ESET DEFENSOR ID]

  Exact relationship: relationship--1577a79c-5f70-41cc-95bd-2407cfd1acbd
• S0480 Cerberus — malware.

  Cerberus can inject input to grant itself additional permissions without user interaction and to prevent application removal.[Threat Fabric Cerberus][CheckPoint Cerberus]

  Exact relationship: relationship--f776a4da-0fa6-414c-a705-e9e8b419e056
• S0485 Mandrake — malware.

  Mandrake abuses the accessibility service to prevent removing administrator permissions, accessibility permissions, and to set itself as the default SMS handler.[Bitdefender Mandrake]

  Exact relationship: relationship--af55d12a-5f58-4135-90d0-f465a66f7a3f
• S0494 Zen — malware.

  Zen can simulate user clicks on ads and system prompts to create new Google accounts.[Google Security Zen]

  Exact relationship: relationship--afe9e326-01f7-4296-a11b-09cfffd80120
• S0545 TERRACOTTA — malware.

  TERRACOTTA can inject clicks to launch applications, share posts on social media, and interact with WebViews to perform fraudulent actions.[WhiteOps TERRACOTTA]

  Exact relationship: relationship--4761145d-34ac-4b45-a0d6-a09b1907a196
• S1055 SharkBot — malware.

  SharkBot can use input injection via Accessibility Services to simulate user touch inputs, prevent applications from opening, change device settings, and bypass MFA protections.[nccgroup_sharkbot_0322]

  Exact relationship: relationship--5dc4eaca-ff82-412a-a8dd-168de1857d8c
• S1062 S.O.V.A. — malware.

  S.O.V.A. can programmatically tap the screen or swipe.[cleafy_sova_1122]

  Exact relationship: relationship--0b1f2735-97d9-4f4a-9967-9fa1464bb651
• S1094 BRATA — malware.

  BRATA can insert a given string of text into a data field. BRATA can abuse the Accessibility Service to interact with other installed applications and inject screen taps to grant permissions.[securelist_brata_0819][mcafee_brata_0421]

  Exact relationship: relationship--a4e72b4f-7ee4-4ee3-82c9-acc3aedb1f2d
• S1231 GodFather — malware.

  GodFather has abused the Accessibility Service to mimic victims’ actions and to redirect victims to its StubActivity when the victims attempt to use the original, legitimate banking application.[ZimperiumOrtegaPratapagiri_GodFather_Jun2025]

  Exact relationship: relationship--c0121974-44ba-425d-9445-2d6598a5bc66
• S9004 Crocodilus — malware.

  Crocodilus has the ability to perform clicks, swipes (left, right, up and down) on the screen and actions such as “Back,” “Home,” and “Menu.”[ThreatFabric_Crocodilus_March2025]

  Exact relationship: relationship--a67a9c6f-318a-4ca5-aa6a-1d6d88b5d523

• M1011 User Guidance

  Users should be warned against granting access to accessibility features, and to carefully scrutinize applications that request this dangerous permission.

• M1012 Enterprise Policy

  An EMM/MDM can use the Android `DevicePolicyManager.setPermittedAccessibilityServices` method to set an explicit list of applications that are allowed to use Android's accessibility features.