Prompts the user for credentials through a Microsoft Outlook pop-up.12
- Tactics
- Credential Access, Collection
- Platforms
- Linux, macOS, Windows
- Version
- 1.3
- Created
- 11 February 2020
- Last modified
- 12 May 2026
- Contributor
- Matthew Molyett, @s1air, Cisco Talos
Adversaries may mimic common operating system GUI components to prompt users for credentials with a seemingly legitimate prompt. When programs are executed that need additional privileges than are present in the current user context, it is common for the operating system to prompt the user for proper credentials to authorize the elevated privileges for the task (ex: Bypass User Account Control).
GUI Input Capture MITRE reference T1056.002
2 groups have been recorded using this technique. Newest first; each entry carries MITRE’s procedure text and a link to the group’s full record. Click a name to filter the rules below.
Has presented victims with spoofed Windows Authentication prompts to collect their credentials.12
All 2 groups for this technique
13 software entries are documented implementing this technique. MITRE files each as a tool or as malware; newest first, then by how many groups carry them.
Has displayed a fake Windows Security dialog box to prompt for Windows credentials.1
Has displayed a fake Windows Security dialog to gather credentials.1
Has captured passwords by prompting victims with a “macOS needs to access System Settings” GUI window.1
Can monitor browser activity for online banking actions and display full-screen overlay images to block user access to the intended site or present additional data fields.12
SILENTTRINITY's credphisher.py module can prompt a current user for their credentials.1
Prompts the user to input credentials using a native macOS dialog box leveraging the system process /Applications/Safari.app/Contents/MacOS/SafariForWebKitDevelopment.1
All 13 software entries for this technique · 6 newest in this preview
Offense vs defense T1056.002
Is defensive coverage keeping up with adversary use? Eight counts, each ranked against all 697 ATT&CK techniques. Attack sits left, defense right, so a shape leaning left means adversaries are better documented here than defenders are equipped. Hover any spoke for its percentile and the share of techniques that have more. The timeline below shows when each side arrived.
How it got here
Adversary activity (campaign spans) over cumulative rule output. Each source is plotted independently from zero, so neither line includes the other. Campaign dates are year-granularity.
GUI Input Capture detection strategy DET0521
MITRE names one behaviour worth catching for this technique and breaks it into 3 analytics, one per platform. Each carries the log sources it needs and the fields you tune per environment.
Behavioral Detection of Spoofed GUI Credential Prompts
AN1440 · Windows
Detects suspicious use of PowerShell, .NET, or script interpreters to spawn processes that mimic UAC prompts, often with credential capture dialogue boxes invoked from non-standard parent processes.
Log sources
The data this analytic draws on. You do not need every component — each one you already collect covers part of it. Each links to its ATT&CK record.
| Data component | Name | Channel |
|---|---|---|
| Process CreationDC0032 | WinEventLog:Sysmon | EventCode=1 |
| Command ExecutionDC0064 | WinEventLog:PowerShell | EventCode=4103, 4104, 4105, 4106 |
Tunable fields
MITRE calls these the analytic’s mutable elements: the thresholds and filters you set for your own environment.
| Field | What you tune |
|---|---|
| CommandLine | Tunable to detect suspicious prompts like 'Enter your password' or 'CredentialRequired' |
| ParentProcessName | Tune to flag UI prompts spawned from unexpected processes like cmd.exe or user scripts |
| TimeWindow | Scope correlation of script execution and prompt appearance |
AN1441 · Linux
Detects GUI-based credential prompts invoked via zenity/kdialog/dialog or X11 APIs from non-user-facing scripts or background shell sessions, often with authentication-related text.
Log sources
The data this analytic draws on. You do not need every component — each one you already collect covers part of it. Each links to its ATT&CK record.
| Data component | Name | Channel |
|---|---|---|
| Process CreationDC0032 | auditd:SYSCALL | execve |
| Command ExecutionDC0064 | linux:cli | Terminal Command History |
Tunable fields
MITRE calls these the analytic’s mutable elements: the thresholds and filters you set for your own environment.
| Field | What you tune |
|---|---|
| ExecutableName | Filter zenity/kdialog prompts launched from unexpected parent shells |
| PromptString | Look for 'password', 'authentication required', or similar tokens |
AN1442 · macOS
Detects AppleScript or Objective-C usage to generate fake authentication windows (e.g., using display dialog or NSAlert) from user-launched or persistence-related processes.
Log sources
The data this analytic draws on. You do not need every component — each one you already collect covers part of it. Each links to its ATT&CK record.
| Data component | Name | Channel |
|---|---|---|
| Script ExecutionDC0029 | macos:unifiedlog | subsystem=com.apple.Security or com.apple.applescript |
| Process CreationDC0032 | macos:osquery | process_events |
Tunable fields
MITRE calls these the analytic’s mutable elements: the thresholds and filters you set for your own environment.
| Field | What you tune |
|---|---|
| ScriptContent | AppleScript snippets like 'display dialog' or 'with hidden answer' |
| ProcessPath | Tune out Apple-signed and expected automation tasks |
Use user training as a way to bring awareness and raise suspicion for potentially malicious events and dialog boxes (ex: Office documents prompting for credentials).
Tests from Atomic Red Team (MIT licence) · technique definition