Input Capture

Adversaries may capture user input to obtain credentials or other information from the user through various methods.

Malware may masquerade as a legitimate third-party keyboard to record user keystrokes.[1] On both Android and iOS, users must explicitly authorize the use of third-party keyboard apps. Users should be advised to use extreme caution before granting this authorization when it is requested.

On Android, malware may abuse accessibility features to record keystrokes by registering an AccessibilityService class, overriding the onAccessibilityEvent method, and listening for the AccessibilityEvent.TYPE_VIEW_TEXT_CHANGED event type. The event object passed into the function will contain the data that the user typed.

Additional methods of keylogging may be possible if root access is available.

ID: T1417
Sub-techniques:  No sub-techniques
Tactic Type: Post-Adversary Device Access
Platforms: Android, iOS
Version: 2.1
Created: 25 October 2017
Last Modified: 24 June 2020
Provided by LAYER 8

Procedure Examples

ID Name Description
S0422 Anubis

Anubis has a keylogger that works in every application installed on the device.[2]

S0655 BusyGasper

BusyGasper can collect every user screen tap and compare the input to a hardcoded list of coordinates to translate the input to a character.[3]

S0480 Cerberus

Cerberus can record keystrokes.[4]

S0478 EventBot

EventBot can abuse Android’s accessibility service to record the screen PIN.[5]

S0522 Exobot

Exobot has used web injects to capture users’ credentials.[6]

S0408 FlexiSpy

FlexiSpy can record keystrokes and analyze them for keywords.[7]

S0406 Gustuff

Gustuff abuses accessibility features to intercept all interactions between a user and the device.[8]

S0407 Monokle

Monokle can record the user's keystrokes.[9]

G0112 Windshift

Windshift has included keylogging capabilities as part of Operation ROCK.[10]


ID Mitigation Description
M1005 Application Vetting

Applications that attempt to register themselves as a device keyboard or request the android.permission.BIND_ACCESSIBILITY_SERVICE permission in a service declaration should be closely scrutinized during the vetting process.

M1012 Enterprise Policy

When using Samsung Knox, third-party keyboards must be explicitly added to an allow list in order to be available to the end-user.[11]

M1011 User Guidance

Users should be weary of granting applications dangerous or privacy-intrusive permissions, such as keyboard registration and accessibility permissions requests.


On Android, users can view and manage which applications have third-party keyboard access through the device settings in System -> Languages & input -> Virtual keyboard. On iOS, users can view and manage which applications have third-party keyboard access through the device settings in General -> Keyboard. On Android, users can view and manage which applications can use accessibility services through the device settings in Accessibility. The exact device settings menu locations may vary between operating system versions.