Screen Capture

From ATT&CK
Jump to: navigation, search
Screen Capture
Technique
ID T1113
Tactic Collection
Platform Windows Server 2003, Windows Server 2008, Windows Server 2012, Windows XP, Windows 7, Windows 8, Windows Server 2003 R2, Windows Server 2008 R2, Windows Server 2012 R2, Windows Vista, Windows 8.1
Data Sources API monitoring, Process monitoring, File monitoring

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.

Examples

  • APT28 regularly deploys a custom tool to take regular screenshots of victims.1
  • Malware used by Group5 is capable of watching the victim's screen.2
  • TinyZBot contains screen capture functionality.3
  • CosmicDuke takes periodic screenshots and exfiltrates them.4
  • ZLib has the ability to obtain screenshots of the compromised system.5
  • BlackEnergy is capable of taking screenshots.6
  • Rover takes screenshots of the compromised system's desktop and saves them to C:\system\screenshot.bmp for exfiltration every 60 minutes.7
  • Trojan.Karagany can take a desktop screenshot and save the file into \ProgramData\Mail\MailAg\shot.png.8
  • T9000 can take screenshots of the desktop and target application windows, saving them to user directories as one byte XOR encrypted .dat files.9
  • Prikormka contains a module that captures screenshots of the victim's desktop.10
  • Crimson contains a command to perform screen captures.11
  • BADNEWS has a command to take a screenshot and send it to the C2 server.12

Mitigation

Blocking software based on screen capture functionality may be difficult, and there may be legitimate software that performs those actions. Instead, identify potentially malicious software that may have functionality to acquire screen captures, and audit and/or block it by using whitelisting13 tools, like AppLocker,1415 or Software Restriction Policies16 where appropriate.17

Detection

Monitoring for screen capture behavior will depend on the method used to obtain data from the operating system and write output files. Detection methods could include collecting information from unusual processes using API calls used to obtain image data, and monitoring for image files written to disk. The sensor data may need to be correlated with other events to identify malicious activity, depending on the legitimacy of this behavior within a given network environment.

References