T1056

Input Capture

Adversaries may use methods of capturing user input to obtain credentials or collect information. During normal system usage, users often provide credentials to various different locations, such as login pages/portals or 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 (e.g. Web Portal Capture). Common sub-techniques include keylogging via Windows hooks (SetWindowsHookEx), GUI input capture via credential dialog spoofing, web portal capture via fake login pages, and credential API hooking via DLL injection into authentication processes. Threat actors including APT42, Storm-1811, and APT39 have leveraged these techniques, as have malware families such as InvisibleFerret, Chaes, Kobalos, and NPPSPY.

Microsoft Sentinel / Defender
kusto
// T1056 Input Capture — Multi-Signal Detection
// Covers: Network Provider DLL registration (NPPSPY), suspicious DLL loads into credential processes,
// input hook API usage, and clipboard/keyboard monitoring process activity
let SuspiciousInputAPIs = dynamic([
  "SetWindowsHookEx", "GetAsyncKeyState", "GetKeyState", "GetRawInputData",
  "pyWinhook", "pynput", "keyboard.hook", "InputCapture",
  "WH_KEYBOARD", "WH_KEYBOARD_LL", "WH_MOUSE_LL"
]);
let CredentialProcesses = dynamic(["winlogon.exe", "lsass.exe", "LogonUI.exe", "consent.exe", "credui.exe"]);
// Signal 1: Suspicious network provider DLL registration (NPPSPY technique)
let NetworkProviderReg = DeviceRegistryEvents
| where Timestamp > ago(24h)
| where ActionType in ("RegistryValueSet", "RegistryKeyCreated")
| where RegistryKey has @"SYSTEM\CurrentControlSet\Control\NetworkProvider\Order"
    or (RegistryKey has @"SYSTEM\CurrentControlSet\Services" and RegistryKey endswith @"\NetworkProvider")
| where InitiatingProcessFileName !in~ ("services.exe", "svchost.exe", "msiexec.exe", "TrustedInstaller.exe")
| extend SignalType = "NetworkProviderRegistration"
| project Timestamp, DeviceName, AccountName, SignalType,
    RegistryKey, RegistryValueName, RegistryValueData,
    InitiatingProcessFileName, InitiatingProcessCommandLine, InitiatingProcessFolderPath;
// Signal 2: Suspicious DLL loaded into credential/authentication processes
let HookDLLLoad = DeviceImageLoadEvents
| where Timestamp > ago(24h)
| where InitiatingProcessFileName in~ (CredentialProcesses)
| where FolderPath !startswith @"C:\Windows\System32\\"
    and FolderPath !startswith @"C:\Windows\SysWOW64\\"
    and FolderPath !startswith @"C:\Program Files\\"
    and FolderPath !startswith @"C:\Program Files (x86)\\"
| where FileName endswith ".dll"
| extend SignalType = "SuspiciousDLLInCredentialProcess"
| project Timestamp, DeviceName, AccountName=InitiatingProcessAccountName, SignalType,
    FileName, FolderPath, SHA256,
    InitiatingProcessFileName, InitiatingProcessCommandLine, InitiatingProcessFolderPath;
// Signal 3: Process creation with input capture indicators
let InputCaptureProcess = DeviceProcessEvents
| where Timestamp > ago(24h)
| where ProcessCommandLine has_any (SuspiciousInputAPIs)
    or (FileName has_any ("keylog", "keyscan", "hookdll", "inputcap", "credcap"))
    or (FolderPath !startswith @"C:\Windows\" and FolderPath !startswith @"C:\Program Files"
        and (ProcessCommandLine has "GetClipboard" or ProcessCommandLine has "Get-Clipboard")
        and ProcessCommandLine has_any ("while", "loop", "sleep", "timer", "interval"))
| extend SignalType = "InputCaptureAPIOrTool"
| project Timestamp, DeviceName, AccountName, SignalType,
    FileName, FolderPath, ProcessCommandLine,
    InitiatingProcessFileName, InitiatingProcessCommandLine, InitiatingProcessFolderPath;
// Signal 4: Process injection into Winlogon or credential UI (common for hooking)
let WinlogonInjection = DeviceEvents
| where Timestamp > ago(24h)
| where ActionType == "CreateRemoteThreadApiCall" or ActionType == "ProcessInjection"
| where AdditionalFields has_any ("winlogon.exe", "LogonUI.exe", "credui.exe", "consent.exe")
| extend SignalType = "InjectionIntoCredentialProcess"
| project Timestamp, DeviceName, AccountName, SignalType,
    FileName, ProcessCommandLine=AdditionalFields,
    InitiatingProcessFileName, InitiatingProcessCommandLine, InitiatingProcessFolderPath;
// Union all signals
union isfuzzy=true NetworkProviderReg, HookDLLLoad, InputCaptureProcess, WinlogonInjection
| sort by Timestamp desc
high severity medium confidence

Data Sources

Process: Process Creation Process: OS API Execution Windows Registry: Windows Registry Key Modification Module: Module Load Process: Process Access Microsoft Defender for Endpoint

Required Tables

DeviceRegistryEvents DeviceImageLoadEvents DeviceProcessEvents DeviceEvents

False Positives

  • Legitimate accessibility software (screen readers, on-screen keyboards, Dragon NaturallySpeaking) that register low-level keyboard hooks via SetWindowsHookEx
  • Enterprise security products (DLP agents, PAM tools like CyberArk) that monitor credential entry as a security control — these load DLLs into credential processes
  • Password managers (1Password, Bitwarden, KeePass) that hook input fields for autofill functionality
  • Keyboard remapping utilities (AutoHotkey, SharpKeys, Microsoft PowerToys) that legitimately intercept and redirect keystrokes
  • Remote desktop and KVM software (TeamViewer, AnyDesk, VNC) that capture keyboard/mouse input for remote transmission
  • Custom enterprise single-sign-on (SSO) credential providers legitimately registered as network providers in HKLM\SYSTEM\CurrentControlSet\Control\NetworkProvider\Order

Unlock Pro Content

Get the full detection package for T1056 including response playbook, investigation guide, and atomic red team tests.

Response PlaybookInvestigation GuideHunting QueriesAtomic Red Team TestsTuning Guidance

Related Detections