T1056.004_credential-api-hooking

T1056.004 Credential API Hooking

Sub-technique of: T1056

High-Level Description

Adversaries may hook into Windows application programming interface (API) functions and Linux system functions to collect user credentials. Malicious hooking mechanisms may capture API or function calls that include parameters that reveal user authentication credentials. Unlike Keylogging, this technique focuses specifically on API functions that include parameters that reveal user credentials.

In Windows, hooking involves redirecting calls to these functions and can be implemented via:

• Hooks procedures, which intercept and execute designated code in response to events such as messages, keystrokes, and mouse inputs.
• Import address table (IAT) hooking, which use modifications to a process’s IAT, where pointers to imported API functions are stored.
• Inline hooking, which overwrites the first bytes in an API function to redirect code flow.

In Linux and macOS, adversaries may hook into system functions via the LD_PRELOAD (Linux) or DYLD_INSERT_LIBRARIES (macOS) environment variables, which enables loading shared libraries into a program’s address space. For example, an adversary may capture credentials by hooking into the libc read function leveraged by SSH or SCP.

Kill Chain Phase

• Collection (TA0009)
• Credential Access (TA0006)

Platforms: Windows, Linux, macOS

What to Check

• Identify if Credential API Hooking technique is applicable to target environment
• Check Windows systems for indicators of Credential API Hooking
• Check Linux systems for indicators of Credential API Hooking
• Check macOS systems for indicators of Credential API Hooking
• Assess detection coverage (1 detection strategies)

How to Test

Atomic Red Team Tests

The following tests are from Atomic Red Team and provide actionable ways to test this technique:

Atomic Test 1: Hook PowerShell TLS Encrypt/Decrypt Messages

Hooks functions in PowerShell to read TLS Communications

Supported Platforms: windows Elevation Required: Yes

mavinject $pid /INJECTRUNNING "#{file_name}"
Invoke-WebRequest #{server_name} -UseBasicParsing

Dependencies:

• T1056.004x64.dll must exist on disk at specified location (#{file_name})

Manual Testing

If Atomic Red Team tests are not applicable, manually verify the technique by:

1. Identify Attack Surface: Determine if the target environment is susceptible to Credential API Hooking by examining the target platforms (Windows, Linux, macOS).

2. Assess Existing Defenses: Review whether mitigations for T1056.004 are in place. If defenses are absent or misconfigured, this technique may be exploitable.

3. Execute Test: Use tools and methods described in the MITRE ATT&CK page and external references below.

Remediation Guide

No specific mitigations documented for this technique.

Detection

Detection of Credential Harvesting via API Hooking

Risk Assessment

CWE Categories

References

• EyeofRa Detecting Hooking June 2017
• Zairon Hooking Dec 2006
• GMER Rootkits
• MWRInfoSecurity Dynamic Hooking 2015
• Elastic Process Injection July 2017
• Intezer Symbiote 2022
• HighTech Bridge Inline Hooking Sept 2011
• Microsoft TrojanSpy:Win32/Ursnif.gen!I Sept 2017
• Microsoft Hook Overview
• Microsoft Process Snapshot
• PreKageo Winhook Jul 2011
• Jay GetHooks Sept 2011
• StackExchange Hooks Jul 2012
• Adlice Software IAT Hooks Oct 2014
• Volatility Detecting Hooks Sept 2012
• Atomic Red Team - T1056.004
• MITRE ATT&CK - T1056.004