Skip to content
New

DeepSeek V4.1 Flash free for 7 days: 10M tokens a day after a top-up of $10 or more. Until Nov 30.

How it works
mukul975/hunting-for-data-staging-before-exfiltrationDFIR and threat hunting

hunting-for-data-staging-before-exfiltration

⁨Detect data-staging activity (MITRE ATT&CK T1074) by analyzing EDR/Sysmon process-creation and file-system telemetry (Event ID 4688, Sysmon 1/11) for 7-Zip/RAR/tar archive creation, unusual temp or hidden folder access, and anomalous consolidation of files from multiple directories. Use when hunting⁩

v1.03 installs+3 in 7 days36.3K StarsApache-2.0synced 12 hours ago

Install

No NotHoly CLI yet? Install it first.

$ curl -fsSL https://notholy.com/install.sh | sh
$ notholy skills install mukul975/hunting-for-data-staging-before-exfiltration

Writes to ⁦~/.notholy/skills⁩ after checking the signature and the SHA-256.

SignatureSigned, ed25519
7piPuFk3AI…lHyZOnDQ==The CLI checks the SHA-256 and the signature before it writes a file.
Packagef5e88a3b…7a654eb8
f5e88a3b90aa…df0e7a654eb84 files · ⁦8.7 KB⁩
ScanMedium2 findings
  • Executable script shipped with the skillscripts/agent.py
  • Links to outside domains
See the full scan
Sourcegithub.com/mukul975/Anthropic-Cybersecurity-Skills/tree/main/skills/hunting-for-data-staging-before-exfiltration@54a7988

Overview

Before exfiltrating data, adversaries typically stage collected files in a central location (MITRE ATT&CK T1074). This involves creating archives with tools like 7-Zip, RAR, or tar, consolidating files from multiple directories, and using temporary or hidden staging directories. This skill detects staging behavior by analyzing process creation logs for archiver activity, monitoring file system events in common staging paths, and identifying anomalous file consolidation patterns.

When to Use

  • When investigating security incidents that require hunting for data staging before exfiltration
  • When building detection rules or threat hunting queries for this domain
  • When SOC analysts need structured procedures for this analysis type
  • When validating security monitoring coverage for related attack techniques

Prerequisites

  • EDR or Sysmon telemetry with process creation and file system events
  • Windows Event Logs (Event ID 4688) or Sysmon Event ID 1, 11
  • Python 3.8+ with standard library
  • Access to process creation logs in JSON/CSV format

Steps

  1. Detect Archive Tool Execution — Monitor for 7z.exe, rar.exe, tar, zip, and WinRAR process creation with compression arguments
  2. Identify Staging Directories — Flag file writes to common staging locations (Recycle Bin, %TEMP%, ProgramData, hidden directories)
  3. Detect Large File Consolidation — Identify patterns of multiple file reads followed by writes to a single directory
  4. Monitor Sensitive Path Access — Track bulk reads from document directories, database paths, and network shares
  5. Analyze Archive Metadata — Extract and analyze archive file sizes, creation times, and source paths
  6. Score Staging Risk — Apply heuristic scoring based on archive size, source diversity, staging path suspicion, and timing
  7. Generate Hunt Report — Produce a structured report with staging event timeline and MITRE ATT&CK mapping

Expected Output

  • JSON report of detected staging events with risk scores
  • Archive creation timeline with source file analysis
  • MITRE ATT&CK mapping (T1074.001, T1074.002, T1560)
  • Staging directory heat map showing suspicious write activity

Files in this version

Permissions

PermissionDeclaredFound by the scan
Reads filesNoNo
Writes filesNoNo
Runs shell commandsYesYes
Uses the networkYesYes
Uses connectorsNoNo
Drives a browserNoNo

Scan findings

Reviewed on Nov 13, 2026

  1. MediumFile · Executable script shipped with the skillscripts/agent.py
  2. InfoLink · Links to outside domains

A clean scan lowers the risk but does not prove a package is safe. Read what you install.

VersionPublishedCommitSHA-256SignaturePermission change
v1.0Nov 13, 202654a7988f5e88a3bSigned–

Ask anything your scope allows.

Create an account, add credits and ask the first question in the chat or the terminal.

  1. 1/3

    Create the account

    Individual or company. You can switch to a company later without losing balance or keys.

    IndividualCompany
  2. 2/3

    Add credits

    By card. Pay per token, no subscription.

    $5.00minimum deposit
  3. 3/3

    Ask

    In the chat, or install the CLI and run notholy login in your terminal.

    $ notholy login