[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M73C59514959JC6FRHY853V5":3,"skill-same:01M73C59514959JC6FRHY853V5":112},{"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":16,"sourceHtmlUrl":17,"categories":18,"keywords":19,"publishedAt":20,"linkOnly":21,"markdownContent":22,"markdownBody":23,"frontMatter":24,"refName":54,"commitSha":55,"skillDirectory":56,"forksCount":57,"repositoryHtmlUrl":58,"repositoryHomepageUrl":59,"ownerHtmlUrl":60,"ownerBlogUrl":61,"ownerDescription":62,"updatedAt":63,"install":64,"resources":77},"01M73C59514959JC6FRHY853V5","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.","Horonomos-laps\u002FYana-AI","Horonomos-laps","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F355299122?v=4","01M76B3QPXE88ET2SQPDPVATZT"," Horonomos-laps","01M72ZQRJPCYPSSWT4D00VJR2A",13,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fhunting-for-command-and-control-beaconing\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fhunting-for-command-and-control-beaconing\u002FSKILL.md",[],[],"2026-11-11 15:11:14",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\nsource: https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\nsource_commit: 04450304b12645cb2b974ab96d28c0664758a88d\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":25,"author":32,"domain":33,"source":34,"license":15,"version":35,"nist_csf":36,"subdomain":26,"description":7,"mitre_attack":41,"source_commit":47,"d3fend_techniques":48},[26,27,28,29,30,31],"threat-hunting","mitre-attack","c2","beaconing","network-analysis","proactive-detection","mahipal","cybersecurity","https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills","1.0",[37,38,39,40],"DE.CM-01","DE.AE-02","DE.AE-07","ID.RA-05",[42,43,44,45,46],"T1046","T1057","T1082","T1083","T1071","04450304b12645cb2b974ab96d28c0664758a88d",[49,50,51,52,53],"File Metadata Consistency Validation","Certificate Analysis","Application Protocol Command Analysis","Content Format Conversion","File Content Analysis","main","481dcd7dd2e288b9d627a2bd017db70e64e6c6fa","core\u002Fskills\u002Fhunting-for-command-and-control-beaconing",2,"https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI","https:\u002F\u002Fyana.vutam.link\u002F","https:\u002F\u002Fgithub.com\u002FHoronomos-laps","https:\u002F\u002Fyana.vutam.link","An open-source governed runtime & execution environment for multi-agent AI systems.","2026-11-14 13:24:09",{"source":8,"skillName":5,"commands":65,"prompt":75,"zipAvailable":76},[66,69,72],{"tool":67,"command":68},"npx","npx skills add Horonomos-laps\u002FYana-AI --skill hunting-for-command-and-control-beaconing",{"tool":70,"command":71},"bunx","bunx skills add Horonomos-laps\u002FYana-AI --skill hunting-for-command-and-control-beaconing",{"tool":73,"command":74},"pnpm","pnpm dlx skills add Horonomos-laps\u002FYana-AI --skill hunting-for-command-and-control-beaconing","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fhunting-for-command-and-control-beaconing\u002FSKILL.md",true,[78,84,88,94,98,102,108],{"path":79,"resourceType":80,"resourceTypeDesc":81,"sizeBytes":82,"sourceHtmlUrl":83},"assets\u002Ftemplate.md","ASSET","资产文件",996,"https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fhunting-for-command-and-control-beaconing\u002Fassets\u002Ftemplate.md",{"path":85,"resourceType":85,"resourceTypeDesc":86,"sizeBytes":87,"sourceHtmlUrl":16},"LICENSE","许可证",11255,{"path":89,"resourceType":90,"resourceTypeDesc":91,"sizeBytes":92,"sourceHtmlUrl":93},"references\u002Fapi-reference.md","REFERENCE","参考文档",2222,"https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fhunting-for-command-and-control-beaconing\u002Freferences\u002Fapi-reference.md",{"path":95,"resourceType":90,"resourceTypeDesc":91,"sizeBytes":96,"sourceHtmlUrl":97},"references\u002Fstandards.md",3224,"https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fhunting-for-command-and-control-beaconing\u002Freferences\u002Fstandards.md",{"path":99,"resourceType":90,"resourceTypeDesc":91,"sizeBytes":100,"sourceHtmlUrl":101},"references\u002Fworkflows.md",4360,"https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fhunting-for-command-and-control-beaconing\u002Freferences\u002Fworkflows.md",{"path":103,"resourceType":104,"resourceTypeDesc":105,"sizeBytes":106,"sourceHtmlUrl":107},"scripts\u002Fagent.py","SCRIPT","脚本",6213,"https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fhunting-for-command-and-control-beaconing\u002Fscripts\u002Fagent.py",{"path":109,"resourceType":104,"resourceTypeDesc":105,"sizeBytes":110,"sourceHtmlUrl":111},"scripts\u002Fprocess.py",14852,"https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fhunting-for-command-and-control-beaconing\u002Fscripts\u002Fprocess.py",[113,121,128,136,144,152],{"skillNo":114,"name":115,"nameZh":6,"description":116,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":117,"licenseFileUrl":6,"sourceHtmlUrl":118,"categories":119,"keywords":120,"publishedAt":20},"01M735GKET5YVYKAY62W2P5YXB","openai--sentry--sentry","Use when the user asks to inspect Sentry issues or events, summarize recent production errors, or pull basic Sentry health data via the Sentry API; perform read-only queries with the bundled script and require `SENTRY_AUTH_TOKEN`.","MIT","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fopenai--sentry--sentry\u002FSKILL.md",[],[],{"skillNo":122,"name":123,"nameZh":6,"description":124,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":125,"categories":126,"keywords":127,"publishedAt":20},"01M73DCAP83T17HY7SMGK7MGFE","ito-basket-compare","Compare Itô prediction-market baskets against a user's knowledge base, portfolio notes, financial context, watchlist, or research thesis. Use for read-only basket comparison and gap analysis without investment advice or live trading.","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fito-basket-compare\u002FSKILL.md",[],[],{"skillNo":129,"name":130,"nameZh":6,"description":131,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":132,"sourceHtmlUrl":133,"categories":134,"keywords":135,"publishedAt":20},"01M734CYEMZFDR3KH6SW0JP8TD","implementing-network-traffic-baselining","Build network traffic baselines from NetFlow\u002FIPFIX data using Python pandas for statistical analysis, z-score anomaly detection, and hourly\u002Fdaily traffic pattern profiling","https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fimplementing-network-traffic-baselining\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fimplementing-network-traffic-baselining\u002FSKILL.md",[],[],{"skillNo":137,"name":138,"nameZh":6,"description":139,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":140,"sourceHtmlUrl":141,"categories":142,"keywords":143,"publishedAt":20},"01M73ASZ6NJRJM44Z2P84NGQ3Q","detecting-evasion-techniques-in-endpoint-logs","Detects defense evasion techniques used by adversaries in endpoint logs including log tampering, timestomping, process injection, and security tool disabling. Use when investigating suspicious endpoint behavior, building detection rules for evasion tactics, or conducting threat hunting for stealthy adversary activity. Activates for requests involving evasion detection, defense evasion analysis, log tampering detection, or MITRE ATT&CK TA0005.","https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fdetecting-evasion-techniques-in-endpoint-logs\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fdetecting-evasion-techniques-in-endpoint-logs\u002FSKILL.md",[],[],{"skillNo":145,"name":146,"nameZh":6,"description":147,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":148,"sourceHtmlUrl":149,"categories":150,"keywords":151,"publishedAt":20},"01M734AFNXD06Z78QRK0VKGT7Q","implementing-microsegmentation-with-guardicore","Implementing microsegmentation using Akamai Guardicore Segmentation to map application dependencies, create granular network policies, visualize east-west traffic flows, and enforce least-privilege communication between workloads across data centers and cloud.","https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fimplementing-microsegmentation-with-guardicore\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fimplementing-microsegmentation-with-guardicore\u002FSKILL.md",[],[],{"skillNo":153,"name":154,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":155,"categories":156,"keywords":157,"publishedAt":20},"01M736TK27QMCXK0DVCH25SJN5","ramdisk-tmpfs-patterns","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Framdisk-tmpfs-patterns\u002FSKILL.md",[],[]]