Conducted large-scale data exfiltration in the Stryker operation, consistent with automated or scripted collection against enterprise systems.1
Automated Collection T1119
- Tactic
- Collection
- Platforms
- IaaS, Linux, macOS, Office Suite, SaaS, Windows
- Version
- 1.4
- Created
- 31 May 2017
- Last modified
- 12 May 2026
- Contributors
- Praetorian; Arun Seelagan, CISA
Once established within a system or network, an adversary may use automated techniques for collecting internal data. Methods for performing this technique could include use of a Command and Scripting Interpreter to search for and copy information fitting set criteria such as file type, location, or name at specific time intervals.
Automated Collection MITRE reference T1119
21 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.
Delivered a PowerShell script capable of recursively scanning victim machines looking for various file types before exfiltrating identified files via HTTP.1
Used a custom tool, sql.net4.exe, to query SQL databases and then identify and extract personally identifiable information.1
Engages in mass collection from compromised systems during intrusions.1
Has used a file stealer to steal documents and images with the following extensions: txt, pdf, png, jpg, doc, xls, xlm, odp, ods, odt, rtf, ppt, xlsx, xlsm, docx, pptx, and jpeg.1
All 21 groups for this technique · 6 newest in this preview
6 campaigns have been recorded using this technique. Listed newest first; dates are year-granularity and attribution is MITRE’s.
During the Anthropic AI-orchestrated Campaign, the adversary used Claude Code to automatically collect and process large volumes of data from without human direction.1
During SharePoint ToolShell Exploitation, threat actors used a command shell to automatically iterate through web.config files to expose and collect machineKey settings.12
Included collection of packet capture and system configuration information.1
Used tools such as SQLULDR2 and PINEGROVE to gather local system and database information.1
During Frankenstein, the threat actors used Empire to automatically gather the username, domain name, machine name, and other system information.1
During Operation Wocao, threat actors used a script to collect information about the infected system.1
All 6 campaigns for this technique
48 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 the ability to automatically compile gathered credentials from configuration files and password vaults within an archive and exfiltrate stolen data leveraging both a primary and fallback C2.1
Can identify and collect credentials across over 50 file paths in Cloud, CI/CD, developer tooling, and container enviornments.12
Can recursively copy files from targeted directories on victim hosts.12
Has the ability to automatically collect host data, secrets, system information, and endpoints.123
Has automated collection of various information including cryptocurrency wallet details.1
Attempts to identify and collect mail login data from Thunderbird and Outlook following execution.1234
All 48 software entries for this technique · 6 newest in this preview
Offense vs defense T1119
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.
Automated Collection detection strategy DET0186
MITRE names one behaviour worth catching for this technique and breaks it into 4 analytics, one per platform. Each carries the log sources it needs and the fields you tune per environment.
Automated File and API Collection Detection Across Platforms
AN0531 · Windows
Automated execution of native utilities and scripts to discover, enumerate, and exfiltrate files and clipboard content. Focus is on detecting repeated file access, scripting engine use, and use of command-line utilities commonly leveraged by collection scripts.
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 |
| File CreationDC0039 | WinEventLog:Sysmon | EventCode=11 |
Tunable fields
MITRE calls these the analytic’s mutable elements: the thresholds and filters you set for your own environment.
| Field | What you tune |
|---|---|
| TimeWindow | Defines the lookback period for identifying burst activity or patterns in process/file events. |
| SuspiciousFileExtensions | Tunable list of file extensions associated with collection (e.g., .pdf, .docx). |
| ProcessCountThreshold | The number of times a process executes before considered anomalous. |
AN0532 · Linux
Repeated or automated access to user document directories or clipboard using shell scripts or utilities like xclip/pbpaste. Detectable via auditd syscall logs or osquery file events.
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 |
| File AccessDC0055 | auditd:SYSCALL | open |
Tunable fields
MITRE calls these the analytic’s mutable elements: the thresholds and filters you set for your own environment.
| Field | What you tune |
|---|---|
| AccessPath | Tunable location for sensitive files like /home/*/Documents. |
| ScriptInterpreterList | Shells or scripting engines to monitor (e.g., bash, python, perl). |
AN0533 · macOS
Use of pbpaste, AppleScript, or third-party automation frameworks (e.g., Automator) to collect clipboard or file content in bursts. Observable via unified logs.
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=launchservices |
| Process CreationDC0032 | macos:unifiedlog | logMessage contains pbpaste or osascript |
Tunable fields
MITRE calls these the analytic’s mutable elements: the thresholds and filters you set for your own environment.
| Field | What you tune |
|---|---|
| AutomationTool | Detectable script interpreters or clipboard tools (pbpaste, osascript). |
| ClipboardCheckRate | Threshold for how often clipboard access occurs within a given time window. |
AN0534 · SaaS
Suspicious sign-ins to Graph API or sensitive resources using non-browser scripting agents (e.g., Python, PowerShell), often for programmatic access to mailbox or OneDrive content.
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 |
|---|---|---|
| User Account AuthenticationDC0002 | azure:signinlogs | Operation=UserLogin |
Tunable fields
MITRE calls these the analytic’s mutable elements: the thresholds and filters you set for your own environment.
| Field | What you tune |
|---|---|
| UserAgentFilter | Filter for scripting agents (e.g., Python, PowerShell) which may vary by org. |
| ExpectedClientIPList | Set of known internal or managed IPs to filter benign automation. |
| DeviceProperties | Expected managed device profiles used to detect unmanaged devices. |
Encryption and off-system storage of sensitive information may be one way to mitigate collection of files, but may not stop an adversary from acquiring the information if an intrusion persists over a long period of time and the adversary is able to discover and access the data through other means. Strong passwords should be used on certain encrypted documents that use them to prevent offline cracking through Brute Force techniques.
Encryption and off-system storage of sensitive information may be one way to mitigate collection of files, but may not stop an adversary from acquiring the information if an intrusion persists over a long period of time and the adversary is able to discover and access the data through other means.
Tests from Atomic Red Team (MIT licence) · technique definition