Has staged captured credentials in var/log/ldapd<unique_keyword>.2.gz.1
- Tactic
- Collection
- Platforms
- ESXi, Linux, macOS, Windows
- Version
- 1.2
- Created
- 13 March 2020
- Last modified
- 12 May 2026
- Contributor
- Massimiliano Romano, BT Security
Adversaries may stage collected data in a central location or directory on the local system prior to Exfiltration. Data may be kept in separate files or combined into one file through techniques such as Archive Collected Data. Interactive command shells may be used, and common functionality within cmd and bash may be used to copy data into a staging location.
Local Data Staging MITRE reference T1074.001
28 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 locally staged captured credentials for subsequent manual exfiltration.1
Has used the folder, C:\\windows\\temp\\s\\, to stage data for exfiltration.1
Has staged data on compromised systems prior to exfiltration often in C:\Users\Public.1
Has saved stolen files including the ntds.dit database and the SYSTEM and SECURITY Registry hives locally to the C:\Windows\Temp\ directory.12
Has utilized the following temporary folders on compromised Windows and Linux systems for their operations prior to exfiltration: C:\Windows\Temp and /tmp.12
All 28 groups for this technique · 6 newest in this preview
13 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 stage extracted data and operational documentation in structured markdown files on local systems prior to exfiltration.1
During SharePoint ToolShell Exploitation, threat actors staged stolen data from web.config files to debug_dev.js.12
During the 2025 Poland Wiper Attacks, the adversaries compiled discovery data locally on the victim host in a file located within C:\Windows\TEMP\outlog.txt.1
During Operation MidnightEclipse, threat actors copied files to the web application folder on compromised devices for exfiltration.1
Involved exporting data from Oracle databases to local CSV files prior to exfiltration.1
Leviathan stored captured credential material on local log files on victim systems during Leviathan Australian Intrusions.1
All 13 campaigns for this technique · 6 newest in this preview
95 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 created a staging file in /tmp for collected data.1
Has stored collected credentials in C:\Users\Public\Downloads\lp-notes.txt.1
Can save collected data and files of interest in C:\ProgramData\info\ to consolidate for exfiltration.12
Has stored stolen credentials on the local machine in %TEMP%\31558.txt.1
Has collected stolen web cookies locally in the %TEMP% folder.1
Has stored stolen credentials for future use in the temp folder of a victimized Ivanti Connect Secure VPN device, specifically in the file location /tmp/cmmmap.kumMW.12
All 95 software entries for this technique · 6 newest in this preview
Offense vs defense T1074.001
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.
Local Data Staging detection strategy DET0261
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.
Detection of Local Data Staging Prior to Exfiltration
AN0724 · Windows
Detects file reads across locations followed by writes to temp or staging directories, often compressed or encrypted, indicating local staging behavior.
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 |
| File AccessDC0055 | WinEventLog:Security | EventCode=4663, 4670, 4656 |
Tunable fields
MITRE calls these the analytic’s mutable elements: the thresholds and filters you set for your own environment.
| Field | What you tune |
|---|---|
| StagingDirList | Paths such as C:\Temp, C:\Windows\Tasks, etc. |
| ArchivingToolPatterns | Matches to 7z.exe, rar.exe, zip.exe, or custom scripts. |
| TimeWindow | How long to correlate file reads followed by compression. |
AN0725 · Linux
Detects aggregation of files from different directories into /tmp, /mnt, or user-specified directories with archiving tools like tar or gzip.
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 |
|---|---|
| StagingDirs | e.g., /tmp, /var/tmp, custom user dirs |
| ArchiveUtilities | tar, gzip, zip, 7z |
| UserThreshold | Number of files or size written in short time |
AN0726 · macOS
Detects staged data aggregated in /Users/Shared, /private/tmp with compression tools like ditto or zip, initiated via Terminal or AppleScript.
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 | exec logs |
| File AccessDC0055 | macos:unifiedlog | file 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 |
|---|---|
| StagingTargets | Shared dirs commonly abused for local collection |
| CompressionBinaries | zip, tar, ditto |
| TimeWindow | Seconds/minutes between source file read and output staging write |
AN0727 · ESXi
Detects local staging behavior via snapshot creation or files written into VMFS partitions by scripts or unauthorized shell access.
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 |
|---|---|---|
| Snapshot CreationDC0057 | esxi:vmkernel | snapshot create/write events |
| Command ExecutionDC0064 | esxi:shell | CLI usage logs |
Tunable fields
MITRE calls these the analytic’s mutable elements: the thresholds and filters you set for your own environment.
| Field | What you tune |
|---|---|
| SnapshotThreshold | Rapid creation or deletion of snapshots |
| CLIInvoker | Unexpected CLI/script invocation outside maintenance windows |
| VMFSWriteRate | Volume of data written locally in short time |
Tests from Atomic Red Team (MIT licence) · technique definition