Cross-source coverage

T1111 / ATT&CK

Multi-Factor Authentication Interception

2 rules across 2 sources.

From MITRE ATT&CK 19.2

Adversaries may target multi-factor authentication (MFA) mechanisms, (i.e., smart cards, token generators, etc.) to gain access to credentials that can be used to access systems, services, and network resources. Use of MFA is recommended and provides a higher level of security than usernames and passwords alone, but organizations should be aware of techniques that could be used to intercept and bypass these security mechanisms.

If a smart card is used for multi-factor authentication, then a keylogger will need to be used to obtain the password associated with a smart card during normal use. With both an inserted card and access to the smart card password, an adversary can connect to a network resource using the infected system to proxy the authentication with the inserted hardware token.

Adversaries may also employ a keylogger to similarly target other hardware tokens, such as RSA SecurID. Capturing token input (including a user's personal identification code) may provide temporary access (i.e. replay the one-time passcode until the next value rollover) as well as possibly enabling adversaries to reliably predict future authentication values (given access to both the algorithm and any seed values used to generate appended temporary codes).

Other methods of MFA may be intercepted and used by an adversary to authenticate. It is common for one-time codes to be sent via out-of-band communications (email, SMS). If the device and/or service is not secured, then it may be vulnerable to interception. Service providers can also be targeted: for example, an adversary may compromise an SMS messaging service in order to steal MFA codes sent to users’ phones.

Platforms
Linux · macOS · Windows
Telemetry
WinEventLog:SysmonWinEventLog:Securitylinux:syslogmacos:unifiedlogmacos:osquery

How MITRE says to detect it DET0246

Detection Strategy for MFA Interception via Input Capture and Smart Card Proxying

Windows Analytic 0687

Behavior chain involving unexpected API calls to capture keyboard input, driver loads for keyloggers, or remote use of smart card authentication via logon sessions not initiated by local user interaction

  • WinEventLog:Sysmon EventCode=10
  • WinEventLog:Security EventCode=4624, 4648
  • WinEventLog:Sysmon EventCode=13, 14

Linux Analytic 0688

Detection of unauthorized keylogger behavior through access to `/dev/input`, loading kernel modules (e.g., via insmod), or polling user input devices from non-user shells

  • linux:syslog syscalls (open, read, ioctl) on /dev/input or /proc/*/fd/*
  • linux:syslog dmesg or syslog for module loads

macOS Analytic 0689

Processes accessing TCC-protected input APIs or polling HID services without user interaction, or dynamically loaded keylogging frameworks using accessibility privileges

  • macos:unifiedlog com.apple.securityd, com.apple.tccd
  • macos:osquery query: process_events, launchd, and tcc.db access

elastic/detection-rules

1 rule
Detection Severity Format
Attempted Bypass of Okta MFA High Elastic TOML

panther-labs/panther-analysis

1 rule
Detection Severity Format
AppOmni Alert Passthrough Medium Panther Python

Detection rules belong to the projects that publish them and remain under their own licenses. This site indexes and links to them; it claims no rights in them.