hunting-for-command-and-control-beaconing

Detect command-and-control beaconing patterns in Zeek-derived network logs.

Updated Apr 23, 2026
One-click install
npx skills add https://github.com/YukiIto1999/ctf-sleuth --skill hunting-for-command-and-control-beaconing
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: hunting-for-command-and-control-beaconing
Source: https://github.com/YukiIto1999/ctf-sleuth/tree/main/.claude/skills/hunting-for-command-and-control-beaconing
Command: npx skills add https://github.com/YukiIto1999/ctf-sleuth --skill hunting-for-command-and-control-beaconing

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill enables proactive detection of command-and-control beaconing patterns in network telemetry, helping security teams identify compromised endpoints through periodic, anomaly-based traffic analysis.

Core Features & Use Cases

  • Frequency analysis of connection timings to reveal regular beaconing intervals.
  • Jitter detection and domain reputation checks to differentiate C2 activity from legitimate traffic.
  • Output formats: machine-readable JSON findings and human-readable Markdown reports for incident response.

Quick Start

Run the hunting workflow against Zeek/HTTP/DNS logs to surface beaconing indicators.

Frequently Asked Questions about hunting-for-command-and-control-beaconing

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I detect C2 beaconing patterns in Zeek logs?

Detect C2 beaconing in Zeek logs by analyzing connection timings, jitter, and domain entropy across dns.log, http.log, and conn.log. This Skill applies heuristic thresholds to interval variance and payload consistency to surface periodic, data-exfiltration-like beacons from compromised endpoints.

What is command-and-control beaconing in network traffic?

Command-and-control beaconing is periodic, anomaly-based network communication where compromised endpoints regularly contact a C2 server. This Skill identifies these patterns by analyzing frequency, jitter, and domain reputation in HTTP, DNS, and long-duration connections to reveal infected devices.

Can I use this beacon detection on HTTP and DNS traffic without long-duration connections?

Yes, the workflow supports standalone HTTP and DNS beacon detection. While it analyzes long-duration connections from conn.log, it independently applies payload consistency and domain entropy heuristics to HTTP and DNS telemetry to identify C2 activity.

How do I differentiate legitimate network traffic from C2 beaconing activity?

Differentiate legitimate traffic from C2 beaconing by analyzing interval variance, jitter, and domain reputation. This Skill applies heuristic thresholds to connection frequencies and payload consistency in network telemetry to isolate anomalous, periodic communication patterns.

What output formats are generated when hunting for C2 beacons?

Hunting for C2 beacons exports findings in machine-readable JSON and human-readable Markdown formats. These outputs provide structured indicators and narrative reports to support incident response and compromised endpoint remediation.