hunting-for-data-exfiltration-indicators

Hunt for data exfiltration through network traffic analysis, detecting unusual data flows, DNS tunneling, cloud storage uploads, and encrypted channel abuse.

Works with

Claude CodeCursorClineWindsurfCodexGooseGitHub CopilotZed

0

total installs

0

this week

8.6K

GitHub stars

0

upvotes

Install Skill

Run in your terminal

$npx skills install mukul975/Anthropic-Cybersecurity-Skills/hunting-for-data-exfiltration-indicators

0

installs

0

this week

8.6K

stars

Installation Guide

How to use hunting-for-data-exfiltration-indicators on Cursor

AI-first code editor with Composer

1

Prerequisites

Before installing skills in Cursor, ensure your development environment meets these requirements:

  • Cursor installed and configured on your machine
  • Node.js 16+ with npm — verify with node --version
  • Active project directory where you want to add hunting-for-data-exfiltration-indicators
2

Run the install command

Execute the skills CLI command in your project's root directory to begin installation:

$npx skills install mukul975/Anthropic-Cybersecurity-Skills/hunting-for-data-exfiltration-indicators

Fetches hunting-for-data-exfiltration-indicators from mukul975/Anthropic-Cybersecurity-Skills and configures it for Cursor.

3

Select Cursor when prompted

The CLI shows a list of agents. Use arrow keys and space to select Cursor:

◆ Which agents do you want to install to?
│ ── Universal (.agents/skills) ────────────────
│ · Cline · Codex · Goose · Windsurf
│ ●Cursor(selected)
│ · Cursor · Aider · Continue
4

Verify installation

Confirm successful installation by checking the skill directory location:

.cursor/skills/hunting-for-data-exfiltration-indicators

Restart Cursor to activate hunting-for-data-exfiltration-indicators. Access via /hunting-for-data-exfiltration-indicators in your agent's command palette.

Security Notice

We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.

Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.

Documentation

name
hunting-for-data-exfiltration-indicators
description
Hunt for data exfiltration through network traffic analysis, detecting unusual data flows, DNS tunneling, cloud storage uploads, and encrypted channel abuse.
domain
cybersecurity
subdomain
threat-hunting
tags
- threat-hunting - mitre-attack - data-exfiltration - dlp - network-analysis - proactive-detection
version
'1.0'
author
mahipal
license
Apache-2.0
atlas_techniques
- AML.T0024 - AML.T0056
nist_ai_rmf
- MEASURE-2.7 - MAP-5.1 - MANAGE-2.4
d3fend_techniques
- File Metadata Consistency Validation - Certificate Analysis - Application Protocol Command Analysis - Content Format Conversion - File Content Analysis
nist_csf
- DE.CM-01 - DE.AE-02 - DE.AE-07 - ID.RA-05

Hunting for Data Exfiltration Indicators

When to Use

  • When hunting for data theft in compromised environments
  • After detecting unusual outbound data volumes or patterns
  • When investigating potential insider threat data theft
  • During incident response to determine what data was stolen
  • When threat intel indicates data exfiltration campaigns targeting your sector

Prerequisites

  • Network proxy/firewall logs with byte-level data transfer metrics
  • DLP solution or CASB with cloud upload visibility
  • DNS query logs for DNS exfiltration detection
  • Email gateway logs for attachment monitoring
  • SIEM with data volume anomaly detection capabilities

Workflow

  1. Define Exfiltration Channels: Identify potential channels (HTTP/S uploads, DNS tunneling, email attachments, cloud storage, removable media, encrypted protocols).
  2. Baseline Normal Data Flows: Establish baseline outbound data transfer volumes per user, host, and destination over a 30-day window.
  3. Detect Volume Anomalies: Identify hosts or users transferring significantly more data than baseline to external destinations.
  4. Analyze Transfer Destinations: Check destination domains/IPs against threat intel, identify newly registered domains, personal cloud storage, and foreign infrastructure.
  5. Inspect Protocol Abuse: Look for DNS tunneling (large/frequent TXT queries), ICMP tunneling, or data hidden in allowed protocols.
  6. Correlate with File Access: Link exfiltration indicators to file access events on sensitive file shares, databases, or repositories.
  7. Report and Contain: Document findings with evidence, estimate data exposure, and recommend containment actions.

Key Concepts

ConceptDescription
T1041Exfiltration Over C2 Channel
T1048Exfiltration Over Alternative Protocol
T1048.001Exfiltration Over Symmetric Encrypted Non-C2
T1048.002Exfiltration Over Asymmetric Encrypted Non-C2
T1048.003Exfiltration Over Unencrypted/Obfuscated Non-C2
T1567Exfiltration Over Web Service
T1567.002Exfiltration to Cloud Storage
T1052Exfiltration Over Physical Medium
T1029Scheduled Transfer
T1030Data Transfer Size Limits (staging)
T1537Transfer Data to Cloud Account
T1020Automated Exfiltration

Tools & Systems

ToolPurpose
SplunkSIEM for data volume analysis and SPL queries
ZeekNetwork metadata for data flow analysis
Microsoft Defender for Cloud AppsCASB for cloud exfiltration
NetskopeCloud DLP and exfiltration detection
SuricataNetwork IDS for protocol anomaly detection
RITADNS exfiltration and beacon detection
ExtraHopNetwork traffic analysis for data flow

Common Scenarios

  1. Cloud Storage Exfiltration: User uploads sensitive documents to personal Google Drive or Dropbox via browser.
  2. DNS Tunneling: Malware exfiltrates data encoded in DNS subdomain queries to attacker-controlled nameserver.
  3. HTTPS Upload: Compromised system POSTs large data blobs to C2 server over encrypted HTTPS.
  4. Email Attachment Exfiltration: Insider forwards sensitive documents to personal email accounts.
  5. Staging and Compression: Adversary stages data in compressed archives before slow exfiltration to avoid detection.

Output Format

Hunt ID: TH-EXFIL-[DATE]-[SEQ]
Exfiltration Channel: [HTTP/DNS/Email/Cloud/USB]
Source: [Host/User]
Destination: [Domain/IP/Service]
Data Volume: [Bytes/MB/GB]
Time Period: [Start - End]
Protocol: [HTTPS/DNS/SMTP/SMB]
Files Involved: [Count/Types]
Risk Level: [Critical/High/Medium/Low]
Confidence: [High/Medium/Low]

List & Monetize Your Skill

Submit your Claude Code skill and start earning

Get started →

Use Cases

Exploratory Data Analysis

Quickly understand datasets, identify patterns, and generate insights

Example

Analyze CSV with 100K rows, identify outliers, visualize correlations, suggest hypotheses

Reduce EDA time from hours to minutes, uncover insights faster

Data Cleaning & Transformation

Write scripts to clean messy data, handle missing values, normalize formats

Example

Generate Python/SQL to fix date formats, impute missing values, remove duplicates

Automate 80% of data preprocessing work

Statistical Analysis

Perform hypothesis testing, regression, and statistical modeling

Example

Run A/B test analysis, calculate confidence intervals, interpret p-values

Get statistically sound analysis without PhD in statistics

Data Visualization

Create charts, dashboards, and visual reports

Example

Generate matplotlib/seaborn code for time series plots, distribution charts, heatmaps

Build presentation-ready visualizations 3x faster

Implementation Guide

Prerequisites

  • Claude Desktop or compatible AI client
  • Python environment (pandas, numpy, matplotlib) or SQL database access
  • Basic understanding of data analysis concepts
  • Sample datasets for testing skill capabilities

Time Estimate

20-40 minutes to set up and run first analysis

Steps

  1. 1Install data analysis skill using provided command
  2. 2Prepare a sample dataset (CSV, JSON, or database connection)
  3. 3Start with descriptive statistics: 'Summarize this dataset'
  4. 4Progress to visualization: 'Create a scatter plot of X vs Y'
  5. 5Advanced analysis: 'Run linear regression and interpret results'
  6. 6Validate outputs: check calculations, verify visualizations make sense
  7. 7Document analysis workflow for reproducibility

Common Pitfalls

  • Not validating statistical assumptions before applying tests
  • Accepting visualizations without checking data accuracy
  • Overlooking data quality issues (missing values, outliers)
  • Misinterpreting correlation as causation
  • Using wrong statistical test for data distribution
  • Not considering sample size and statistical power

Best Practices

✓ Do

  • +Always validate data quality before analysis
  • +Check statistical assumptions (normality, independence, etc.)
  • +Visualize data before running statistical tests
  • +Document analysis steps for reproducibility
  • +Cross-validate findings with domain experts
  • +Use skill for initial exploration, then dive deeper manually
  • +Save generated code for reuse on similar datasets

✗ Don't

  • Don't trust analysis without verifying data quality
  • Don't apply statistical tests without checking assumptions
  • Don't make business decisions solely on AI-generated analysis
  • Don't ignore outliers without investigating cause
  • Don't skip data validation and sanity checks
  • Don't use for mission-critical financial or medical analysis without expert review

💡 Pro Tips

  • Describe data context: 'This is user behavior data from e-commerce site'
  • Ask for interpretation: 'What does this correlation mean for business?'
  • Request multiple approaches: 'Show 3 ways to handle missing data'
  • Combine AI analysis with domain expertise for best insights
  • Use for rapid prototyping, then refine analysis manually

When to Use This

✓ Use when

Use for exploratory data analysis, data cleaning, statistical testing, visualization prototyping, and learning new analysis techniques. Best for initial exploration and rapid insights.

✗ Avoid when

Avoid for mission-critical financial analysis, medical research requiring regulatory compliance, production ML models, or when deep statistical expertise is required for nuanced interpretation.

Learning Path

  1. 1Basic: descriptive statistics, data cleaning, simple visualizations
  2. 2Intermediate: hypothesis testing, regression, correlation analysis
  3. 3Advanced: time series analysis, clustering, predictive modeling
  4. 4Expert: causal inference, experimental design, advanced statistical methods

Related Skills

Reviews

4.666 reviews
  • C
    Chaitanya PatilDec 24, 2024

    Registry listing for hunting-for-data-exfiltration-indicators matched our evaluation — installs cleanly and behaves as described in the markdown.

  • A
    Alexander FarahDec 12, 2024

    Solid pick for teams standardizing on skills: hunting-for-data-exfiltration-indicators is focused, and the summary matches what you get after install.

  • N
    Nikhil FarahDec 12, 2024

    hunting-for-data-exfiltration-indicators reduced setup friction for our internal harness; good balance of opinion and flexibility.

  • C
    Charlotte OkaforDec 8, 2024

    Registry listing for hunting-for-data-exfiltration-indicators matched our evaluation — installs cleanly and behaves as described in the markdown.

  • R
    Ren RamirezDec 4, 2024

    Keeps context tight: hunting-for-data-exfiltration-indicators is the kind of skill you can hand to a new teammate without a long onboarding doc.

  • M
    Min GonzalezNov 27, 2024

    hunting-for-data-exfiltration-indicators fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

  • A
    Alexander ThompsonNov 27, 2024

    hunting-for-data-exfiltration-indicators reduced setup friction for our internal harness; good balance of opinion and flexibility.

  • D
    Diego PatelNov 23, 2024

    I recommend hunting-for-data-exfiltration-indicators for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.

  • P
    Piyush GNov 15, 2024

    hunting-for-data-exfiltration-indicators reduced setup friction for our internal harness; good balance of opinion and flexibility.

  • A
    Alexander AbebeNov 3, 2024

    hunting-for-data-exfiltration-indicators has been reliable in day-to-day use. Documentation quality is above average for community skills.

showing 1-10 of 66

1 / 7

Discussion

Comments — not star reviews
  • No comments yet — start the thread.