dns-and-beacon-analytics-beacon-periodicity — Claude Code skill
dns-and-beacon-analytics-beacon-periodicity is a Claude Code skill that inspects network connection cadences for repetitive C2 callbacks. It measures interval jitter through order statistics.
no license ★ 73 updated 2026-11-15
npx skills add W4L33Dx/Cyber-Monster --skill dns-and-beacon-analytics-beacon-periodicity -a claude-codeWhat dns-and-beacon-analytics-beacon-periodicity does
This skill checks check-in frequency against implant sleep cycles using median intervals, median absolute deviation, and quartile skewness. These order statistics resist single dropped packets and retransmissions better than mean averages. When packet padding is absent, the skill also tracks payload byte consistency across sessions.
Evaluation requires at least ten consecutive callbacks. Shorter sequences are ignored to prevent mistaking temporary user traffic bursts for automated implant beacons. For DNS traffic, raw evidence must come from endpoint logs or span taps because local caching resolvers erase the original query cadence.
If interval or timing telemetry is missing, the analysis yields an inconclusive telemetry gap rather than a clean verdict.
What it helps with
- detect hidden periodic callbacks in raw connection records
- calculate interval jitter and dispersion using median statistics
- filter out legitimate multi-host heartbeats from single-host beacons
- identify payload size consistency across repetitive check-ins
Example prompts for the agent
- Inspect connection timestamps for beaconing patterns and calculate interval jitter
- Run periodicity detection across the extracted DNS queries for this host
- Evaluate interval dispersion on this ten-event connection series
How to install dns-and-beacon-analytics-beacon-periodicity
1Skills CLI (Vercel)
npx skills add W4L33Dx/Cyber-Monster --skill dns-and-beacon-analytics-beacon-periodicity -a claude-code2Manually: put the files in place
~/.claude/skills/dns-and-beacon-analytics-beacon-periodicity/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/dns-and-beacon-analytics-beacon-periodicity/
1Skills CLI (Vercel)
npx skills add W4L33Dx/Cyber-Monster --skill dns-and-beacon-analytics-beacon-periodicity -a codex2Manually: put the files in place
.agents/skills/dns-and-beacon-analytics-beacon-periodicity/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add W4L33Dx/Cyber-Monster --skill dns-and-beacon-analytics-beacon-periodicity -a cursor2Manually: put the files in place
.cursor/skills/dns-and-beacon-analytics-beacon-periodicity/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install W4L33Dx/Cyber-Monster blue-team/detection-and-monitoring/dns-and-beacon-analytics-beacon-periodicity2Manually: put the files in place
.github/skills/dns-and-beacon-analytics-beacon-periodicity/SKILL.md1Skills CLI (Vercel)
npx skills add W4L33Dx/Cyber-Monster --skill dns-and-beacon-analytics-beacon-periodicity -a gemini-cli2Platform CLI
gemini skills install https://github.com/W4L33Dx/Cyber-Monster --path blue-team/detection-and-monitoring/dns-and-beacon-analytics-beacon-periodicityManually: put the files in place
.devin/skills/dns-and-beacon-analytics-beacon-periodicity/SKILL.mdThe legacy .windsurf/skills/ path still works
Claude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about dns-and-beacon-analytics-beacon-periodicity
How to install dns-and-beacon-analytics-beacon-periodicity in Claude Code?
Run npx skills add W4L33Dx/Cyber-Monster --skill dns-and-beacon-analytics-beacon-periodicity -a claude-code.
What does dns-and-beacon-analytics-beacon-periodicity do?
It spots automated implant check-ins by measuring interval clustering and jitter across connection sequences. The analysis uses order statistics to stay accurate despite network retries.
What telemetry is required for dns-and-beacon-analytics-beacon-periodicity?
It requires ordered connection timestamps and byte counts covering at least ten check-ins. DNS investigations require endpoint query logs or packet captures to bypass resolver caching.