[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7EKVNQAMKB4GY355BT4SABC":3,"skill-same:01M7EKVNQAMKB4GY355BT4SABC":87},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":51,"commitSha":52,"skillDirectory":53,"forksCount":54,"repositoryHtmlUrl":55,"repositoryHomepageUrl":6,"ownerHtmlUrl":56,"ownerBlogUrl":6,"ownerDescription":57,"updatedAt":58,"install":59,"resources":72},"01M7EKVNQAMKB4GY355BT4SABC","hunting-for-command-and-control-beaconing",null,"Detect C2 beaconing patterns in network traffic using frequency analysis, jitter detection, and domain reputation to identify compromised endpoints communicating with adversary infrastructure.","lza6\u002FArmor-piercing-system-prompts","lza6","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F128880206?v=4","01M7EB3K7WPX5T28EJ2NVHE6EG","Chinese-tingfeng","01M7EB3K97E1KQ16QWKJMFNGX8",11,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F04-安全渗透\u002Fhunting-for-command-and-control-beaconing\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: hunting-for-command-and-control-beaconing\ndescription: Detect C2 beaconing patterns in network traffic using frequency analysis,\n  jitter detection, and domain reputation to identify compromised endpoints communicating\n  with adversary infrastructure.\ndomain: cybersecurity\nsubdomain: threat-hunting\ntags:\n- threat-hunting\n- mitre-attack\n- c2\n- beaconing\n- network-analysis\n- proactive-detection\nversion: '1.0'\nauthor: mahipal\nlicense: Apache-2.0\nd3fend_techniques:\n- File Metadata Consistency Validation\n- Certificate Analysis\n- Application Protocol Command Analysis\n- Content Format Conversion\n- File Content Analysis\nnist_csf:\n- DE.CM-01\n- DE.AE-02\n- DE.AE-07\n- ID.RA-05\nmitre_attack:\n- T1046\n- T1057\n- T1082\n- T1083\n- T1071\n---\n\n# Hunting for Command and Control Beaconing\n\n## When to Use\n\n- When proactively hunting for compromised systems in the network\n- After threat intel indicates C2 frameworks targeting your industry\n- When investigating periodic outbound connections to suspicious domains\n- During incident response to identify active C2 channels\n- When DNS query logs show unusual patterns to specific domains\n\n## Prerequisites\n\n- Network proxy\u002Ffirewall logs with full URL and timing data\n- DNS query logs (passive DNS, DNS server logs, or Sysmon Event ID 22)\n- Zeek\u002FBro network connection logs or NetFlow data\n- SIEM with statistical analysis capabilities (Splunk, Elastic)\n- Threat intelligence feeds for domain\u002FIP reputation\n\n## Workflow\n\n1. **Identify Beaconing Characteristics**: Define what constitutes beaconing (regular intervals, small payload sizes, consistent destinations, jitter patterns).\n2. **Collect Network Telemetry**: Aggregate proxy logs, DNS queries, and connection metadata for analysis.\n3. **Apply Frequency Analysis**: Identify connections with regular intervals using statistical methods (standard deviation, coefficient of variation).\n4. **Filter Known-Good Traffic**: Exclude legitimate periodic traffic (Windows Update, AV updates, heartbeat services, NTP).\n5. **Analyze Domain\u002FIP Reputation**: Check identified beaconing destinations against threat intel, WHOIS data, and certificate transparency logs.\n6. **Investigate Endpoint Context**: Correlate beaconing activity with process creation, user context, and file system changes on source endpoints.\n7. **Confirm and Respond**: Validate C2 activity, block communication, and initiate incident response.\n\n## Key Concepts\n\n| Concept | Description |\n|---------|-------------|\n| T1071 | Application Layer Protocol (HTTP\u002FHTTPS\u002FDNS C2) |\n| T1071.001 | Web Protocols (HTTP\u002FS beaconing) |\n| T1071.004 | DNS (DNS tunneling C2) |\n| T1573 | Encrypted Channel |\n| T1572 | Protocol Tunneling |\n| T1568 | Dynamic Resolution (DGA, fast-flux) |\n| T1132 | Data Encoding in C2 |\n| T1095 | Non-Application Layer Protocol |\n| Beacon Interval | Time between C2 check-ins |\n| Jitter | Random variation in beacon interval |\n| DGA | Domain Generation Algorithm |\n| Fast-Flux | Rapidly changing DNS resolution |\n\n## Tools & Systems\n\n| Tool | Purpose |\n|------|---------|\n| RITA (Real Intelligence Threat Analytics) | Automated beacon detection in Zeek logs |\n| Splunk | Statistical beacon analysis with SPL |\n| Elastic Security | ML-based anomaly detection for beaconing |\n| Zeek\u002FBro | Network connection metadata collection |\n| Suricata | Network IDS with JA3\u002FJA4 fingerprinting |\n| VirusTotal | Domain and IP reputation checking |\n| PassiveDNS | Historical DNS resolution data |\n| Flare | C2 profile detection |\n\n## Common Scenarios\n\n1. **Cobalt Strike Beacon**: HTTP\u002FHTTPS beaconing with configurable sleep time and jitter to malleable C2 profiles.\n2. **DNS Tunneling C2**: Data exfiltration and command receipt via encoded DNS TXT\u002FCNAME queries to attacker-controlled domains.\n3. **Sliver C2 over HTTPS**: Modern C2 framework using HTTPS with configurable beacon intervals and domain fronting.\n4. **DGA-based C2**: Malware generating random domains daily, with adversary registering upcoming domains for C2.\n5. **Legitimate Service Abuse**: C2 over legitimate cloud services (Azure, AWS, Slack, Discord, Telegram).\n\n## Output Format\n\n```\nHunt ID: TH-C2-[DATE]-[SEQ]\nSource IP: [Internal IP]\nSource Host: [Hostname]\nDestination: [Domain\u002FIP]\nProtocol: [HTTP\u002FHTTPS\u002FDNS\u002FCustom]\nBeacon Interval: [Average seconds]\nJitter: [Percentage]\nConnection Count: [Total connections]\nData Volume: [Bytes sent\u002Freceived]\nFirst Seen: [Timestamp]\nLast Seen: [Timestamp]\nDomain Age: [Days]\nTI Match: [Yes\u002FNo - source]\nRisk Level: [Critical\u002FHigh\u002FMedium\u002FLow]\n```\n","# Hunting for Command and Control Beaconing\n\n## When to Use\n\n- When proactively hunting for compromised systems in the network\n- After threat intel indicates C2 frameworks targeting your industry\n- When investigating periodic outbound connections to suspicious domains\n- During incident response to identify active C2 channels\n- When DNS query logs show unusual patterns to specific domains\n\n## Prerequisites\n\n- Network proxy\u002Ffirewall logs with full URL and timing data\n- DNS query logs (passive DNS, DNS server logs, or Sysmon Event ID 22)\n- Zeek\u002FBro network connection logs or NetFlow data\n- SIEM with statistical analysis capabilities (Splunk, Elastic)\n- Threat intelligence feeds for domain\u002FIP reputation\n\n## Workflow\n\n1. **Identify Beaconing Characteristics**: Define what constitutes beaconing (regular intervals, small payload sizes, consistent destinations, jitter patterns).\n2. **Collect Network Telemetry**: Aggregate proxy logs, DNS queries, and connection metadata for analysis.\n3. **Apply Frequency Analysis**: Identify connections with regular intervals using statistical methods (standard deviation, coefficient of variation).\n4. **Filter Known-Good Traffic**: Exclude legitimate periodic traffic (Windows Update, AV updates, heartbeat services, NTP).\n5. **Analyze Domain\u002FIP Reputation**: Check identified beaconing destinations against threat intel, WHOIS data, and certificate transparency logs.\n6. **Investigate Endpoint Context**: Correlate beaconing activity with process creation, user context, and file system changes on source endpoints.\n7. **Confirm and Respond**: Validate C2 activity, block communication, and initiate incident response.\n\n## Key Concepts\n\n| Concept | Description |\n|---------|-------------|\n| T1071 | Application Layer Protocol (HTTP\u002FHTTPS\u002FDNS C2) |\n| T1071.001 | Web Protocols (HTTP\u002FS beaconing) |\n| T1071.004 | DNS (DNS tunneling C2) |\n| T1573 | Encrypted Channel |\n| T1572 | Protocol Tunneling |\n| T1568 | Dynamic Resolution (DGA, fast-flux) |\n| T1132 | Data Encoding in C2 |\n| T1095 | Non-Application Layer Protocol |\n| Beacon Interval | Time between C2 check-ins |\n| Jitter | Random variation in beacon interval |\n| DGA | Domain Generation Algorithm |\n| Fast-Flux | Rapidly changing DNS resolution |\n\n## Tools & Systems\n\n| Tool | Purpose |\n|------|---------|\n| RITA (Real Intelligence Threat Analytics) | Automated beacon detection in Zeek logs |\n| Splunk | Statistical beacon analysis with SPL |\n| Elastic Security | ML-based anomaly detection for beaconing |\n| Zeek\u002FBro | Network connection metadata collection |\n| Suricata | Network IDS with JA3\u002FJA4 fingerprinting |\n| VirusTotal | Domain and IP reputation checking |\n| PassiveDNS | Historical DNS resolution data |\n| Flare | C2 profile detection |\n\n## Common Scenarios\n\n1. **Cobalt Strike Beacon**: HTTP\u002FHTTPS beaconing with configurable sleep time and jitter to malleable C2 profiles.\n2. **DNS Tunneling C2**: Data exfiltration and command receipt via encoded DNS TXT\u002FCNAME queries to attacker-controlled domains.\n3. **Sliver C2 over HTTPS**: Modern C2 framework using HTTPS with configurable beacon intervals and domain fronting.\n4. **DGA-based C2**: Malware generating random domains daily, with adversary registering upcoming domains for C2.\n5. **Legitimate Service Abuse**: C2 over legitimate cloud services (Azure, AWS, Slack, Discord, Telegram).\n\n## Output Format\n\n```\nHunt ID: TH-C2-[DATE]-[SEQ]\nSource IP: [Internal IP]\nSource Host: [Hostname]\nDestination: [Domain\u002FIP]\nProtocol: [HTTP\u002FHTTPS\u002FDNS\u002FCustom]\nBeacon Interval: [Average seconds]\nJitter: [Percentage]\nConnection Count: [Total connections]\nData Volume: [Bytes sent\u002Freceived]\nFirst Seen: [Timestamp]\nLast Seen: [Timestamp]\nDomain Age: [Days]\nTI Match: [Yes\u002FNo - source]\nRisk Level: [Critical\u002FHigh\u002FMedium\u002FLow]\n```\n",{"name":5,"tags":24,"author":31,"domain":32,"license":15,"version":33,"nist_csf":34,"subdomain":25,"description":7,"mitre_attack":39,"d3fend_techniques":45},[25,26,27,28,29,30],"threat-hunting","mitre-attack","c2","beaconing","network-analysis","proactive-detection","mahipal","cybersecurity","1.0",[35,36,37,38],"DE.CM-01","DE.AE-02","DE.AE-07","ID.RA-05",[40,41,42,43,44],"T1046","T1057","T1082","T1083","T1071",[46,47,48,49,50],"File Metadata Consistency Validation","Certificate Analysis","Application Protocol Command Analysis","Content Format Conversion","File Content Analysis","main","d69096e239f2a89aabc2cd078c47664a9d3b1e11","04-安全渗透\u002Fhunting-for-command-and-control-beaconing",3,"https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts","https:\u002F\u002Fgithub.com\u002Flza6","个人vx：Tf00798\r\n个人✈：@TFGY999","2026-10-08 14:29:22",{"source":8,"skillName":5,"commands":60,"prompt":70,"zipAvailable":71},[61,64,67],{"tool":62,"command":63},"npx","npx skills add lza6\u002FArmor-piercing-system-prompts --skill hunting-for-command-and-control-beaconing",{"tool":65,"command":66},"bunx","bunx skills add lza6\u002FArmor-piercing-system-prompts --skill hunting-for-command-and-control-beaconing",{"tool":68,"command":69},"pnpm","pnpm dlx skills add lza6\u002FArmor-piercing-system-prompts --skill hunting-for-command-and-control-beaconing","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F04-安全渗透\u002Fhunting-for-command-and-control-beaconing\u002FSKILL.md",true,[73,79,83],{"path":74,"resourceType":75,"resourceTypeDesc":76,"sizeBytes":77,"sourceHtmlUrl":78},"references\u002Fapi-reference.md","REFERENCE","参考文档",2222,"https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F04-安全渗透\u002Fhunting-for-command-and-control-beaconing\u002Freferences\u002Fapi-reference.md",{"path":80,"resourceType":75,"resourceTypeDesc":76,"sizeBytes":81,"sourceHtmlUrl":82},"references\u002Fstandards.md",3224,"https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F04-安全渗透\u002Fhunting-for-command-and-control-beaconing\u002Freferences\u002Fstandards.md",{"path":84,"resourceType":75,"resourceTypeDesc":76,"sizeBytes":85,"sourceHtmlUrl":86},"references\u002Fworkflows.md",4360,"https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F04-安全渗透\u002Fhunting-for-command-and-control-beaconing\u002Freferences\u002Fworkflows.md",[88,97,102,109,116,123],{"skillNo":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":92,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":96},"01M7FFG485KY83TD6HSC4YPCMC","obsidian-clipper-template-creator","Guide for creating templates for the Obsidian Web Clipper. Use when you want to create a new clipping template, understand available variables, or format clipped content.","MIT","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobsidian-clipper-template-creator\u002FSKILL.md",[],[],"2026-11-16 10:05:34",{"skillNo":98,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":92,"licenseFileUrl":6,"sourceHtmlUrl":99,"categories":100,"keywords":101,"publishedAt":96},"01M7FFG0T6AZ0STEJPSB3CX84K","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobsidian-clipper-template-creator-antigravity-awesome-skills-main\u002FSKILL.md",[],[],{"skillNo":103,"name":104,"nameZh":6,"description":105,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":92,"licenseFileUrl":6,"sourceHtmlUrl":106,"categories":107,"keywords":108,"publishedAt":96},"01M7FFFY0QEM14SKWPDYGMXM2P","python-api","Programmatic Object-Detection-Metrics API guidance for BoundingBox, BoundingBoxes, Evaluator, enums, coordinate conversion, AP\u002FmAP semantics, and source-style import diagnostics.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobject-detection-metrics\u002Fsub-skills\u002Fpython-api\u002FSKILL.md",[],[],{"skillNo":110,"name":111,"nameZh":6,"description":112,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":92,"licenseFileUrl":6,"sourceHtmlUrl":113,"categories":114,"keywords":115,"publishedAt":96},"01M7FFFVZQZ2GJ0C0TGP7JHD20","file-evaluation","Folder-based PASCAL VOC AP\u002FmAP evaluation from ground-truth and detection text files.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobject-detection-metrics\u002Fsub-skills\u002Ffile-evaluation\u002FSKILL.md",[],[],{"skillNo":117,"name":118,"nameZh":6,"description":119,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":92,"licenseFileUrl":6,"sourceHtmlUrl":120,"categories":121,"keywords":122,"publishedAt":96},"01M7FFFSFNYSE77SJ6PE1CK2DA","object-detection-metrics","Guides legacy Object-Detection-Metrics PASCAL VOC AP\u002FmAP evaluation from detection text folders and direct Python API classes.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobject-detection-metrics\u002FSKILL.md",[],[],{"skillNo":124,"name":125,"nameZh":6,"description":126,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":92,"licenseFileUrl":6,"sourceHtmlUrl":127,"categories":128,"keywords":129,"publishedAt":96},"01M7FFFP0GCK1RVXBCPQ8APBMT","nx-workspace-patterns","Configure and optimize Nx monorepo workspaces. Use when setting up Nx, configuring project boundaries, optimizing build caching, or implementing affected commands.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fnx-workspace-patterns\u002FSKILL.md",[],[]]