Has captured screen content during an active Zoom session.1
Screen Capture T1113
- Tactic
- Collection
- Platforms
- Linux, macOS, Windows
- Version
- 1.1
- Created
- 31 May 2017
- Last modified
- 12 May 2026
Adversaries may attempt to take screen captures of the desktop to gather information over the course of an operation. Screen capturing functionality may be included as a feature of a remote access tool used in post-compromise operations. Taking a screenshot is also typically possible through native utilities or API calls, such as CopyFromScreen, xwd, or screencapture.[1][2]
Screen Capture MITRE reference T1113
19 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 used malware, such as GHAMBAR and POWERPOST, to take screenshots.1
Delivered PowerShell scripts capable of taking screenshots of victim machines.1
Has used plugins to take screenshots on targeted systems.1
Has obtained a screenshot of the victim's system using the gdi32.dll and gdiplus.dll libraries.1
Has used the remote monitoring and management tool ConnectWise to obtain screen captures from victim's machines.1
All 19 groups for this technique · 6 newest in this preview
1 campaign has been recorded using this technique. Listed newest first; dates are year-granularity and attribution is MITRE’s.
During the 2025 Poland Wiper Attacks, the adversaries captured screenshots of devices using nircmd console through the command nircmd.exe “savescreenshot C:\Windows\Temp\imagetmp.png.1
All 1 campaigns for this technique
151 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.
The AshTag AshenOrchestrator component has the ability to take screenshots.1
Has obtained screen captures leveraging the screen command which captures, encrypts and uploads the stolen image to the adversary controlled C2 server.1
Has conducted screen capturing.1
All 151 software entries for this technique · 6 newest in this preview
Offense vs defense T1113
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.
Screen Capture detection strategy DET0346
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.
Detect Screen Capture via Commands and API Calls
AN0980 · Windows
Unusual use of screen capture APIs (e.g., CopyFromScreen) or command-line tools to write image files to disk.
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 |
|---|---|---|
| Module LoadDC0016 | WinEventLog:Sysmon | EventCode=7 |
| Process CreationDC0032 | WinEventLog:Sysmon | EventCode=1 |
Tunable fields
MITRE calls these the analytic’s mutable elements: the thresholds and filters you set for your own environment.
| Field | What you tune |
|---|---|
| ParentProcessName | Depends on allowed parent process behaviors in the environment (e.g., explorer.exe vs powershell.exe) |
| TimeWindow | Can tune alert thresholds for rapid or scheduled screenshots (e.g., interval-based screen capture) |
| ImageExtension | To detect file writes (e.g., .bmp, .png) that deviate from typical user activity |
AN0981 · macOS
Invocation of built-in commands like screencapture or use of undocumented APIs from suspicious 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 | macos:unifiedlog | process: exec |
Tunable fields
MITRE calls these the analytic’s mutable elements: the thresholds and filters you set for your own environment.
| Field | What you tune |
|---|---|
| CommandLineRegex | Customize regex for flag detection (e.g., screencapture -x) based on usage patterns |
| ParentProcessName | May vary depending on expected screencapture behavior (Terminal vs remote agent) |
AN0982 · Linux
Use of tools like xwd or import to generate screenshots, especially under non-GUI 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 | auditd:SYSCALL | execve |
Tunable fields
MITRE calls these the analytic’s mutable elements: the thresholds and filters you set for your own environment.
| Field | What you tune |
|---|---|
| TerminalSession | Filter based on TTY sessions or remote terminal usage |
| ExecutablePath | Match against known location of xwd/import binaries or renamed variants |
Tests from Atomic Red Team (MIT licence) · technique definition