Has stolen source code from victim environments including Mistral AI.1
Data from Local System T1005
- Tactic
- Collection
- Platforms
- ESXi, Linux, macOS, Network Devices, Windows
- Version
- 1.8
- Created
- 31 May 2017
- Last modified
- 12 May 2026
- Contributors
- William Cain; Austin Clark, @c2defense; Liran Ravich, CardinalOps
Adversaries may search local system sources, such as file systems, configuration files, local databases, virtual machine files, or process memory, to find files of interest and sensitive data prior to Exfiltration.
Data from Local System MITRE reference T1005
46 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 collected cached data and files from within the victim environment.123
Gathered data and files of interest from victim's systems.1
Has collected data from the local disk of compromised hosts.12
Gathered data from database and other critical servers in victim environments, then used wiping mechanisms as an anti-analysis and anti-forensics mechanism.1
Has run scripts to collect documents from targeted hosts.1
All 46 groups for this technique · 6 newest in this preview
15 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 tasked Claude Code to automatically gather sensitive data stored within the local system to include credentials, system configurations and sensitive operational data.1
During SharePoint ToolShell Exploitation, threat actors extracted information from the compromised systems.1234
During Operation MidnightEclipse, threat actors stole saved cookies and login data from targeted systems.1
During Cutting Edge, threat actors stole the running configuration and cache data from targeted Ivanti Connect Secure VPNs.12
During C0026, the threat actors collected documents from compromised hosts.1
During C0015, the threat actors obtained files and data from the compromised network.1
All 15 campaigns for this technique · 6 newest in this preview
169 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 collect system information and files of interest from compromised systems.12
Has commands that allow the actor download files from the compromised host to the C2 server, and to also download specific sections of a file.1
Has collected local data from a compromised host to include desktop cryptocurrency wallet data, and documents from within Desktop, Documents, and Downloads.1
All 169 software entries for this technique · 6 newest in this preview
Offense vs defense T1005
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.
Data from Local System detection strategy DET0380
MITRE names one behaviour worth catching for this technique and breaks it into 5 analytics, one per platform. Each carries the log sources it needs and the fields you tune per environment.
Detection of Local Data Collection Prior to Exfiltration
AN1070 · Windows
Adversaries collecting local files via PowerShell, WMI, or direct file API calls often include recursive file listings, targeted file reads, and temporary file staging.
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:Security | EventCode=4688 |
| 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 |
|---|---|
| TargetFilePathRegex | Allows tuning for file extensions or paths of sensitive data (e.g., *.xls, *.db, *.pdf). |
| ParentProcessFilter | Used to scope monitoring to suspicious parent/child process trees like PowerShell or WMI spawning file reads. |
AN1071 · Linux
Adversaries using bash scripts or tools to recursively enumerate user home directories, config files, or SSH keys.
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 |
|---|---|
| TimeWindow | Time span to correlate multiple file access events indicative of scripted or bulk access. |
| ScriptToolName | List of tools (e.g., find, grep, tar, scp) that may be benign but are context-sensitive. |
AN1072 · macOS
Adversary use of bash/zsh or AppleScript to locate files and exfil targets like user keychains or documents.
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:spawn |
| File AccessDC0055 | fs:fsusage | read/write |
Tunable fields
MITRE calls these the analytic’s mutable elements: the thresholds and filters you set for your own environment.
| Field | What you tune |
|---|---|
| UserContext | Useful for excluding known admin or scheduled jobs. |
| TargetVolume | Focus monitoring on removable drives or external paths. |
AN1073 · Network Devices
Collection of device configuration via CLI commands (e.g., show running-config, copy flash, more), often followed by TFTP/SCP transfers.
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 |
|---|---|---|
| Command ExecutionDC0064 | networkdevice:cli | command logging |
Tunable fields
MITRE calls these the analytic’s mutable elements: the thresholds and filters you set for your own environment.
| Field | What you tune |
|---|---|
| CommandScope | Defines list of configuration or diagnostic commands to monitor. |
| AuthenticatedUserList | Helps reduce false positives by whitelisting known admins. |
AN1074 · ESXi
Adversaries accessing datastore or configuration files via vim-cmd, esxcli, or SCP to extract logs, VMs, or host configurations.
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 |
|---|---|---|
| File AccessDC0055 | esxis:vmkernel | Datastore Access |
| Command ExecutionDC0064 | esxi:hostd | Command Execution |
Tunable fields
MITRE calls these the analytic’s mutable elements: the thresholds and filters you set for your own environment.
| Field | What you tune |
|---|---|
| AccessPathRegex | Regex for filtering targeted VM paths or files like *.vmdk, *.vmx. |
| InteractiveShellUsage | Tune to distinguish between interactive and script-driven data access. |
Data loss prevention can restrict access to sensitive data and detect sensitive data that is unencrypted.
Tests from Atomic Red Team (MIT licence) · technique definition