STAGING
ARCHIVES
DOUBLE EXTORTION
FILE SERVER
DetectionBlue TeamSOCOctober 12, 2026•9 min read

Detecting Bulk Data Staging Before Double Extortion

Before data leaves, it is collected and compressed. That staging step happens on your hosts, in your logs, and ahead of the egress that tools usually watch.

Scroll

In double-extortion cases the operator copies data first and encrypts later. The collection phase leaves a distinct footprint: an archiver run across file shares, a large password-protected archive appearing in an odd directory, or one account reading far more files than usual. Catching staging can stop both the theft and the encryption.

Signals at a Glance

SignalWhereATT&CK
Archiver with password or recursive flags on a share pathSysmon 1, EDRT1560.001
Large archive created in a temp, public or recycle folderSysmon 11, EDRT1074.001
Single account reading thousands of files in minutes5145, file auditT1039
Staging folder on a server growing rapidlyFile telemetryT1074.002
Unusual archiver binary location or renamed copyEDRT1036

Archiver Behaviour

7-Zip, WinRAR and similar tools are common in IT, so the process alone is not an alert. The combination is: a password flag, a share or user-profile source, and a destination in a location people do not normally archive to:

title: Archiver Staging Data with Password
logsource:
  category: process_creation
  product: windows
detection:
  tool:
    Image|endswith:
      - '\7z.exe'
      - '\7za.exe'
      - '\rar.exe'
      - '\winrar.exe'
  password:
    CommandLine|contains:
      - ' -p'
      - ' -hp'
  recursive:
    CommandLine|contains:
      - ' a '
      - ' -r'
  condition: tool and password and recursive
level: medium
# tune/validate: raise to high when the source path is a file share or the host is a server

Read Volume and Staging Growth

A staging account reads broadly. Count distinct files accessed per account and per source, and compare with that account’s own history:

// Defender / Sentinel (KQL) - large archive written on a server
DeviceFileEvents
| where ActionType == "FileCreated"
| where FileName endswith ".zip" or FileName endswith ".7z" or FileName endswith ".rar"
| where FileSize > 500000000
| join kind=inner (DeviceInfo | where OSPlatform startswith "WindowsServer" | distinct DeviceId) on DeviceId
| project Timestamp, DeviceName, FolderPath, FileName, FileSize, InitiatingProcessAccountName, InitiatingProcessCommandLine
// tune/validate: exclude sanctioned backup and archiving jobs by account and path
Vetted sources

SigmaHQ archive and collection rules, Elastic data-staging detections, Splunk ESCU archive analytics, and CISA #StopRansomware guidance on exfiltration. Backup and archiving jobs are legitimate large-archive writers, so baseline them first.

Build Detections That Fire

Mjolnir Security helps blue teams turn threat intelligence into high-fidelity detections across endpoint, network, identity and cloud telemetry.

Detection EngineeringManaged Detection & ResponseThreat HuntingIncident ResponsePurple Teaming
  • Detection Engineering We build and tune detections mapped to ATT&CK from your own telemetry.
  • Threat Hunting as a Service Hypothesis-driven hunts for the behaviours on this page.
  • 24/7 Incident Response Containment when a detection fires. Call +1 833 403 5875.
Written by: Mjolnir Threat Research (MTAC)  |  Published: October 12, 2026  |  Last reviewed: October 12, 2026