Skill Market

hunting for data staging before exfiltration

Detect data staging activity before exfiltration by monitoring for archive creation with 7-Zip/RAR, unusual temp

GitHub
githubcommunityai-agentsclaude-codecloud-securitycybersecuritydevsecopsethical-hacking
0.0
0 installs33.4K GitHub starsby mukul975

Skill Introduction

Overview
Detect data staging activity before exfiltration by monitoring for archive creation with 7-Zip/RAR, unusual temp

Core value

Turns reusable Debugging know-how into an installable skill, helping users complete github, community, ai-agents, claude-code work faster.

Target users

  • Developers, testers, and maintainers who handle Debugging tasks in Focus Code.
  • Teams that already trust workflows or content from mukul975.
  • Users who want standardized prompts, steps, or conventions instead of repeating setup work.

Best practices

  • Read the skill content first to confirm required inputs, expected outputs, and dependencies.
  • Try it on a small task before relying on it for critical work.
  • Add project-specific constraints such as coding style, target platform, test expectations, and delivery format.
  • For external sources, verify the source link, version, and recent maintenance activity.

Best use cases

  • Tasks related to github, community, ai-agents, claude-code that need a reusable execution flow.
  • Converting a community repo, team convention, or personal workflow into day-to-day assistance.
  • Starting from a proven skill instead of writing prompts or procedures from scratch.

Limits and boundaries

  • Results depend on the quality of the original skill content and may need human correction.
  • It does not replace code review, tests, security review, or professional judgment.
  • External tools, APIs, account permissions, and local dependencies still need separate setup.

Differentiation

  • Structured around Debugging, making it easier to discover and reuse than loose prompt snippets.
  • Marked as GitHub, which helps users judge trust and maintenance expectations.
  • Keeps the original source link available for repository, documentation, or discussion follow-up.
  • Tagged with github, community, ai-agents, claude-code, so it can be filtered by concrete task intent.

Install and use

Install
Copy Install Command
focus install hunting-for-data-staging-before-exfiltration-1dd020
View source

Detail Preview

SKILL.md

Primary filemarkdown3 KB

name: hunting-for-data-staging-before-exfiltration description: Detect data staging activity before exfiltration by monitoring for archive creation with 7-Zip/RAR, unusual temp folder access, large file consolidation, and staging directory patterns via EDR and process telemetry domain: cybersecurity subdomain: threat-hunting tags:

  • data-staging
  • exfiltration
  • t1074
  • archive-detection
  • edr
  • threat-hunting
  • dlp version: '1.0' author: mahipal license: Apache-2.0 d3fend_techniques:
  • File Metadata Consistency Validation
  • Content Format Conversion
  • File Content Analysis
  • Platform Hardening
  • File Format Verification nist_csf:
  • DE.CM-01
  • DE.AE-02
  • DE.AE-07
  • ID.RA-05

Hunting for Data Staging Before Exfiltration

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

Reviews

Overall rating

0.0
0.0

0 comments

No reviews yet