Adversaries may use methods of capturing user input to obtain machine identities and credentials or collect information. During normal system usage, users often provide machine identities and credentials to various different locations, such as system dialog boxes. Input capture mechanisms may be transparent to the user (e.g. Credential API Hooking) or rely on deceiving the user into providing input into what they believe to be a genuine service.
This type of attack technique cannot be easily mitigated with preventive controls since it is based on the abuse of system features.
Detection may vary depending on how input is captured but may include monitoring for certain Windows API calls (e.g.
GetAsyncKeyState), monitoring for malicious instances of Command and Scripting Interpreter, and ensuring no unauthorized drivers or kernel modules that could indicate keylogging or API hooking are present.
Created: 27 December 2020
Last Modified: 27 December 2020