hunting-for-data-staging-before-exfiltration

Detect data staging before exfiltration by analyzing archiver process execution and file system telemetry.

954|172|Updated Mar 13, 2026
One-click install
npx skills add https://github.com/xalgord/xalgorix --skill hunting-for-data-staging-before-exfiltration
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: hunting-for-data-staging-before-exfiltration
Source: https://github.com/xalgord/xalgorix/tree/main/internal/tools/skills/data/threat-hunting/hunting-for-data-staging-before-exfiltration
Command: npx skills add https://github.com/xalgord/xalgorix --skill hunting-for-data-staging-before-exfiltration

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Adversaries typically stage collected files in a central location (MITRE ATT&CK T1074) before exfiltrating them, and security teams often miss this activity because they only watch for archive tools while attackers use renamed binaries or plain copy commands. This Skill provides a structured hunting procedure to surface staging behavior from EDR and Sysmon telemetry before data leaves the environment.

Core Features & Use Cases

  • Archive Tool Detection: Monitor process creation events for 7z.exe, rar.exe, tar, zip, and WinRAR, including renamed binaries matched via OriginalFileName and hashes.
  • Staging Directory Analysis: Flag file writes to common staging paths such as %TEMP%, ProgramData, the Recycle Bin, and hidden directories, plus large file consolidation patterns.
  • Risk Scoring and Reporting: Score staging events by archive size, source diversity, path suspicion, and timing, then produce a JSON report with MITRE ATT&CK mapping (T1074.001, T1074.002, T1560).
  • Use Case: A SOC analyst investigating a suspected breach runs this hunt against Sysmon Event ID 1 and 11 logs to find a burst of file writes into C:\Windows\Temp followed by encrypted 7-Zip archive creation, confirming data staging before exfiltration.

Quick Start

Hunt for data staging activity in my Sysmon process creation and file creation logs and generate a risk-scored report mapped to MITRE ATT&CK T1074.

Frequently Asked Questions about hunting-for-data-staging-before-exfiltration

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I detect data staging before exfiltration?

Monitor process creation logs for archiver tools like 7z.exe, rar.exe, tar, and WinRAR, and watch Sysmon Event ID 11 for bursts of file writes into a single staging directory. Also track bulk reads from document folders and network shares followed by consolidation.

How to detect renamed 7-Zip or RAR binaries in Sysmon logs?

Match the OriginalFileName and Hashes fields in Sysmon Event ID 1 instead of the on-disk Image name. Attackers often rename 7z.exe to something like svchost.exe, which defeats Image-name-based detection rules.

What telemetry is required for data staging threat hunting?

You need EDR or Sysmon telemetry with process creation and file system events, specifically Sysmon Event IDs 1 and 11 or Windows Event ID 4688. Logs should be available in JSON or CSV format, and Python 3.8+ with the standard library is required for analysis.

Why do archive detection rules miss real exfiltration staging?

Attackers often stage data without archivers by using robocopy, xcopy, or Copy-Item to consolidate files into one folder, so no 7z.exe or rar.exe ever runs. Encrypted and split archives also bypass DLP content inspection, making the -p password flag and .7z.001 split patterns stronger signals.

How do I validate that my data staging detection rule works?

Run Atomic Red Team test T1074.001 or manually execute a command like 7z a -p -v25m against a documents folder into a temp path. Confirm that both Sysmon Event ID 1 with the archiver OriginalFileName and Event ID 11 writes to the staging path trigger your rule.

What causes false positives in data staging detection?

Backup jobs like Veeam or nightly robocopy, user-driven WinRAR usage, and installer temp extraction commonly trigger false positives. Tune by baselining parent process, signer, schedule, and whether the staging directory is later read by an upload process.