Back to catalog
Static reviewDevelopment

Skill dossier

hunting-for-beaconing-with-frequency-analysis

Source declaration

Identify command-and-control beaconing patterns in network traffic by applying statistical frequency analysis, jitter calculation, and coefficient of variation scoring to detect periodic callbacks from compromised endpoints.

The author's original description, preserved in English. It describes intent, not verified performance.

Identify command-and-control beaconing patterns in network traffic by applying statistical frequency analysis, jitter calculation, and coefficient of variation scoring to detect periodic callbacks from compromised endpoints.

developmentreferencesscripts

Research summary

Machine-generated analysis; pending human review

These observations come from deterministic source parsing, not a human security review or controlled task evaluation.

Identify command-and-control beaconing patterns in network traffic by applying statistical frequency analysis, jitter calculation, and coefficient of variation scoring to detect periodic callbacks from compromised endpoints. This bilingual summary is generated deterministically from collected source text and file structure; it is pending human editorial review.

Review scope

Deterministic static analysis of collected SKILL.md and supporting text/code. Machine-assisted candidates and findings await human editorial review; no dynamic behavior or effect is assessed.

Observable capabilities

  • Workflow [Source statement; provisional, not tested. Evidence: skills/hunting-for-beaconing-with-frequency-analysis/SKILL.md:L57]

Limitations & scope

  • Static analysis cannot assess runtime behavior, command success, network reachability, or model output quality.
  • No commands, scripts, network requests, model calls, or controlled skill executions were performed.
  • Category, tags, capabilities, workflows, and bilingual editorial summaries are deterministic candidates pending human review, not verified outcomes.
  • Exact token counts are unavailable until a later pipeline performs and records an official model-specific count.

Relevant for

  • Practitioners evaluating whether to inspect and install the source skill; this audience is inferred from the product context, not measured usage. [Evidence: skills/hunting-for-beaconing-with-frequency-analysis/SKILL.md:L1-L37]

What ships with the skill

The file inventory comes from the collected source at the recorded commit. Paths and sizes are structural observations, not a measure of quality.

files
8
Markdown files
5
scripts
2
references
4
Size
45.6 KB
Structural complexity
Low

File inventory

PathTypeBytes
skills/hunting-for-beaconing-with-frequency-analysis/assets/template.mdReference1.6 KB
skills/hunting-for-beaconing-with-frequency-analysis/LICENSEOther11 KB
skills/hunting-for-beaconing-with-frequency-analysis/references/api-reference.mdReference2.6 KB
skills/hunting-for-beaconing-with-frequency-analysis/references/standards.mdReference3.5 KB
skills/hunting-for-beaconing-with-frequency-analysis/references/workflows.mdReference4.7 KB
skills/hunting-for-beaconing-with-frequency-analysis/scripts/agent.pyScript5 KB
skills/hunting-for-beaconing-with-frequency-analysis/scripts/process.pyScript9.3 KB
skills/hunting-for-beaconing-with-frequency-analysis/SKILL.mdInstruction7.8 KB

SKILL.md frontmatter

{
  "name": "hunting-for-beaconing-with-frequency-analysis",
  "description": "Identify command-and-control beaconing patterns in network traffic by applying statistical frequency analysis, jitter calculation, and coefficient of variation scoring to detect periodic callbacks from compromised endpoints.",
  "domain": "cybersecurity",
  "subdomain": "threat-hunting",
  "tags": [
    "threat-hunting",
    "beaconing",
    "c2-detection",
    "frequency-analysis",
    "network-traffic",
    "RITA",
    "jitter-detection",
    "mitre-t1071"
  ],
  "version": "1.0",
  "author": "mahipal",
  "license": "Apache-2.0",
  "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"
  ],
  "mitre_attack": [
    "T1046",
    "T1057",
    "T1082",
    "T1083",
    "T1071"
  ]
}

A reading of the operating sequence

This workflow reconstructs the apparent sequence from source material. Unless controlled evaluation is explicitly recorded, it is provisional—not an observed trace.

  1. 01
    Decision

    When to Use

    Source-described decision candidate under “When to Use”; not verified execution.

  2. 02
    Action

    Workflow

    Source-described action candidate under “Workflow”; not verified execution.

  3. 03
    Action

    Define Beacon Parameters: Establish detection thresholds -- coefficient of variation (CV) below 0.20 indicates strong periodicity, minimum 50 connections over 24 hours, average interval between 30 seconds and 24 hours.

    Source-described action candidate under “Workflow”; not verified execution.

  4. 04
    Action

    Collect Network Telemetry: Aggregate proxy logs, DNS queries, firewall connection logs, and Zeek metadata into the analysis platform.

    Source-described action candidate under “Workflow”; not verified execution.

  5. 05
    Input

    Calculate Connection Intervals: For each source-destination pair, compute the time delta between consecutive connections and derive mean interval, standard deviation, and CV.

    Source-described input candidate under “Workflow”; not verified execution.

  6. 06
    Action

    Apply Jitter Analysis: Sophisticated C2 frameworks like Cobalt Strike add jitter (randomness) to beacon intervals. The Sunburst backdoor beaconed every 15 minutes plus/minus 90 seconds. Analyze jitter patterns to detect even randomized beaconing.

    Source-described action candidate under “Workflow”; not verified execution.

Inspect all extracted workflow candidates (21 candidate steps)
  1. 07
    Action

    Filter Legitimate Periodic Traffic: Exclude known-good beaconing sources including Windows Update, antivirus definition updates, NTP synchronization, SaaS heartbeat services, and CDN health checks.

    Source-described action candidate under “Workflow”; not verified execution.

  2. 08
    Action

    Analyze Data Size Consistency: C2 heartbeat packets typically have consistent payload sizes. Calculate the CV of bytes transferred per connection -- low variance suggests automated communication.

    Source-described action candidate under “Workflow”; not verified execution.

  3. 09
    Action

    Enrich with Threat Intelligence: Check identified beaconing destinations against VirusTotal, WHOIS registration data (flag domains under 30 days old), certificate transparency logs, and passive DNS history.

    Source-described action candidate under “Workflow”; not verified execution.

  4. 10
    Input

    Correlate with Endpoint Telemetry: Map beaconing source IPs to endpoint hostnames via DHCP logs, then correlate with process creation events (Sysmon Event ID 1, 3) to identify the responsible process.

    Source-described input candidate under “Workflow”; not verified execution.

  5. 11
    Action

    Score and Prioritize: Assign risk scores based on CV value, domain age, TI matches, data size consistency, and suspicious port usage. Escalate high-confidence findings.

    Source-described action candidate under “Workflow”; not verified execution.

  6. 12
    Action

    Key Concepts

    Source-described action candidate under “Key Concepts”; not verified execution.

  7. 13
    Action

    Tools & Systems

    Source-described action candidate under “Tools & Systems”; not verified execution.

  8. 14
    Action

    Detection Queries

    Source-described action candidate under “Detection Queries”; not verified execution.

  9. 15
    Action

    Common Scenarios

    Source-described action candidate under “Common Scenarios”; not verified execution.

  10. 16
    Action

    Cobalt Strike Beacon: Default 60-second interval with configurable 0-50% jitter over HTTPS. Malleable C2 profiles can mimic legitimate traffic patterns.

    Source-described action candidate under “Common Scenarios”; not verified execution.

  11. 17
    Action

    Sunburst/SUNSPOT: 12-14 day dormancy period, then beaconing every 12-14 minutes with randomized jitter, designed to evade frequency analysis.

    Source-described action candidate under “Common Scenarios”; not verified execution.

  12. 18
    Action

    DNS Tunneling C2: Encoded data exfiltration via DNS TXT/CNAME queries to attacker-controlled domains, detectable via high subdomain entropy and query volume.

    Source-described action candidate under “Common Scenarios”; not verified execution.

  13. 19
    Action

    Sliver C2: Modern C2 framework with HTTPS, mTLS, and WireGuard protocols, configurable beacon intervals with built-in jitter support.

    Source-described action candidate under “Common Scenarios”; not verified execution.

  14. 20
    Action

    Legitimate Service Abuse: C2 communication over Slack, Discord, Telegram, or cloud storage APIs, making destination-based filtering ineffective.

    Source-described action candidate under “Common Scenarios”; not verified execution.

  15. 21
    Output

    Output Format

    Source-described output candidate under “Output Format”; not verified execution.

Potential risk surfaces

Static findings identify points to inspect before installation. They do not establish that a skill is safe, malicious, or effective.

Items warrant review

61 deterministic lexical finding(s) require review across the collected text. Findings can occur in documentation and do not prove execution or exploitability; binary-only files were not scanned.

Network accessObserved
File writesObserved
Credential useNot observed
Medium

Network access is mentioned

2 occurrences

A URL or network client appears in this source line. Review destinations, data sent, and trust boundaries; static text cannot establish actual network activity. This rule matched 2 location(s) in the collected text; 2 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

Note

File modification is described or implemented

59 occurrences

This line contains a possible file-write or redirection operation. Check destination paths and overwrite behavior; the static review did not write any file. This rule matched 59 location(s) in the collected text; 3 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

Where context can be spent

Discovery, activation, and resource layers have different meanings. Exact values appear only when the official token-counting method was run with a named model.

Exact token counts unavailable

All token values, including per-file inventory, are null until the pipeline performs an official exact count with an explicit model.

No token measurement was recorded with the required official method. This dossier does not substitute character counts, file sizes, or estimates.

Controlled evaluation

No controlled evaluation

This skill has only the evidence identified above. No task success, token efficiency, latency, or quality advantage is claimed.

Not tested

Use with the source in view

Install command
Inspect the pinned source at https://github.com/mukul975/Anthropic-Cybersecurity-Skills/blob/54a798831d2266a3ca61ce68a7acb80b81160d57/skills/hunting-for-beaconing-with-frequency-analysis/SKILL.md and follow the source repository's installation instructions. No installation was performed or verified by this static analyzer. Source license: Apache-2.0.

Prerequisites

  • Static analysis cannot assess runtime behavior, command success, network reachability, or model output quality.
  • No commands, scripts, network requests, model calls, or controlled skill executions were performed.
  • Category, tags, capabilities, workflows, and bilingual editorial summaries are deterministic candidates pending human review, not verified outcomes.
  • Exact token counts are unavailable until a later pipeline performs and records an official model-specific count.

Example prompts

Not provided

A decision, with its limits attached

Strengths

  • The snapshot contains 8 collected file(s), 5 Markdown file(s), and 2 script file(s), enabling source-level inspection. [Evidence: skills/hunting-for-beaconing-with-frequency-analysis/SKILL.md:L1]

Considerations

  • No functional, security, or model-quality result has been established. Human review must inspect source context and all cited findings before installation or publication.
Research conclusion

Provisional deterministic static inventory only; pending human editorial review and, separately, controlled evaluation. No install recommendation, security assurance, or effectiveness claim is made.

Traceable by construction

The dossier is a time-bound reading of a public artifact, not an endorsement. Use the source link to inspect the exact upstream material.

mukul975Anthropic-Cybersecurity-Skillsskills/hunting-for-beaconing-with-frequency-analysis
Source type
Community
Commit
54a798831d2266a3ca61ce68a7acb80b81160d57
Collected
20 Nov 2026
Last checked
20 Nov 2026
Upstream license
Apache-2.0
Repository stars
36,446
Content basis

Deterministic lexical parsing, YAML frontmatter validation, file inventory, source-described workflow extraction, and heuristic provisional classification of the supplied files only. Generated by machine; no LLM, execution, dynamic testing, or human editorial approval.