analyzing-dns-logs-for-exfiltration

analyzing-dns-logs-for-exfiltration is a skill for Claude Code from oyi77/1ai-skills. It costs 74 tokens per session (1,088 once invoked), scanned A, original, MIT.

A security-analysis guide for finding suspicious behavior in DNS query logs. DNS is the system that turns names such as example.com into network addresses, but attackers can also use it to hide commands or stolen data in repeated queries.

In plain words
What is it for?
Use it to investigate possible DNS-based data theft or command channels, including DNS tunneling, algorithmically generated domains, and DNS-over-HTTPS activity.
Why use it?
DNS traffic often passes through networks even when other paths are restricted. Unusual query volumes, long subdomains, generated domains, or high-entropy names can indicate tunneling or malware communication.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the 1ai-skills plugin — 209 skills, 4 commands shipped together

Good fit Use it to investigate possible DNS-based data theft or command channels, including DNS tunneling, algorithmically generated domains, and DNS-over-HTTPS activity.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/oyi77/1ai-skills/analyzing-dns-logs-for-exfiltration
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add oyi77/1ai-skills --skill analyzing-dns-logs-for-exfiltration
Clone the repo
git clone --depth 1 https://github.com/oyi77/1ai-skills

Made for: Claude Code.

Or install 1ai-skills, the plugin that ships this one along with the rest of its 209 skills, 4 commands.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for analyzing-dns-logs-for-exfiltration

README.md
[![agentmods](https://agentmods.dev/badge/skills/oyi77/1ai-skills/analyzing-dns-logs-for-exfiltration/github.svg)](https://agentmods.dev/skills/oyi77/1ai-skills/analyzing-dns-logs-for-exfiltration)
Your own site
<a href="https://agentmods.dev/skills/oyi77/1ai-skills/analyzing-dns-logs-for-exfiltration"><img src="https://agentmods.dev/badge/skills/oyi77/1ai-skills/analyzing-dns-logs-for-exfiltration/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for analyzing-dns-logs-for-exfiltration

Your own site · 80×15
<a href="https://agentmods.dev/skills/oyi77/1ai-skills/analyzing-dns-logs-for-exfiltration"><img src="https://agentmods.dev/badge/skills/oyi77/1ai-skills/analyzing-dns-logs-for-exfiltration.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 74 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,088 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00074 $0.01088
Opus 5 $0.00037 $0.00544
Sonnet 5 $0.00015 $0.00218
Haiku 4.5 $0.00007 $0.00109

Measured 8d ago against content hash c18621b7967f, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

analyzing-dns-logs-for-exfiltration scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 8d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

cybersecurity/analyzing-dns-logs-for-exfiltration/SKILL.md · 127 lines

How it starts

The opening of the file, as written. The whole thing — 127 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Analyzing Dns Logs For Exfiltration

Overview

Cybersecurity skill for analyzing dns logs for exfiltration. Follows industry best practices and security standards.

When to Use

Trigger phrases:

  • "analyzing dns logs for exfiltration"
  • "SOC teams suspect data exfiltration through DNS tunneling to bypass firewall/pro"
  • "Threat intelligence indicates adversaries using DNS-based C2 channels (e"
  • "UEBA detects anomalous DNS query volumes from specific hosts"

Use this skill when:

  • SOC teams suspect data exfiltration through DNS tunneling to bypass firewall/proxy controls
  • Threat intelligence indicates adversaries using DNS-based C2 channels (e.g., Cobalt Strike DNS beacon)
  • UEBA detects anomalous DNS query volumes from specific hosts
  • Malware analysis reveals DNS-over-HTTPS (DoH) or DNS tunneling capabilities

Do not use for standard DNS troubleshooting or availability monitoring — this skill focuses on security-relevant DNS abuse detection.

When NOT to Use

  • When you lack proper authorization for testing
  • For production systems without change management
  • When the task requires legal or compliance expertise beyond technical scope

Prerequisites

  • DNS query logging enabled (Windows DNS Server, Bind, Infoblox, or Cisco Umbrella)
  • DNS logs ingested into SIEM (Splunk with Stream:DNS, dns sourcetype, or Zeek DNS logs)
  • Passive DNS data for historical domain resolution analysis
  • Baseline of normal DNS behavior (query volume, domain distribution, TXT record frequency)
  • Python with math and collections libraries for entropy calculation

Workflow

# Example: IOC detection
import re

IOC_PATTERNS = {
    "ip": r"\b(?:\d{1,3}\.){3}\d{1,3}\b",
    "domain": r"\b[a-z0-9-]+\.[a-z]{2,}\b",
    "hash_md5": r"\b[a-f0-9]{32}\b",
    "hash_sha256": r"\b[a-f0-9]{64}\b",
}

def extract_iocs(text: str) -> dict:
    return {k: re.findall(v, text) for k, v in IOC_PATTERNS.items()}
  1. Scope the Analysis — Define what dns logs artifacts or data sources to examine and the investigation timeline.
  2. Preserve Evidence — Create forensic copies of relevant data. Maintain chain of custody documentation.
  3. Extract Key Indicators — Use exfiltration to parse and extract relevant dns logs data points from collected artifacts.
  4. Correlate Findings — Cross-reference extracted data with other sources (threat intel, logs, timelines).
  5. Build Timeline — Construct a chronological sequence of events related to dns logs.
  6. Document Analysis — Write findings report with evidence, conclusions, and recommendations.

Read the full file on GitHub · 127 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 8d ago First seen · 127 lines · 74 tokens per session scan A c18621b7967f

Subscribe to this mod's changes

analyzing-dns-logs-for-exfiltration is a skill published in the GitHub repository oyi77/1ai-skills (12 stars, last pushed today), licensed MIT. It adds 74 tokens to every session and 1,088 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-04.

Related

Other skills, from other repositories

analyzing-dns-logs-for-exfiltration

Analyzes DNS query logs to detect data exfiltration via DNS tunneling, DGA domain communication, and covert C2 channels using entropy analysis, query volume anomalies, and subdomain length detection in SIEM platforms. Use when SOC teams need to identify DNS-based threats that bypass traditional network security…

mukul975/Anthropic-Cybersecurity-Skills · 73 tokens

analyzing-dns-logs-for-exfiltration

A security-analysis workflow for finding suspicious use of DNS, the system that translates domain names into network addresses. It looks for signs of DNS tunnelling, where data is hidden in DNS requests, as well as algorithmically generated domains and hidden command channels.

killvxk/cybersecurity-skills-zh · 83 tokens

analyzing-dns-logs-for-exfiltration

Analyzes DNS query logs to detect data exfiltration via DNS tunneling, DGA domain communication, and covert C2 channels using entropy analysis, query volume anomalies, and subdomain length detection in SIEM platforms. Use when SOC teams need to identify DNS-based threats that bypass traditional network security…

26zl/cybersec-toolkit · 73 tokens

analyzing-dns-logs-for-exfiltration

Analyzes DNS query logs to detect data exfiltration via DNS tunneling, DGA domain communication, and covert C2 channels using entropy analysis, query volume anomalies, and subdomain length detection in SIEM platforms. Use when SOC teams need to identify DNS-based threats that bypass traditional network security…

adriannoes/awesome-agentic-ai · 73 tokens

analyzing-dns-logs-for-exfiltration

Analyzes DNS query logs to detect data exfiltration via DNS tunneling, DGA domain communication, and covert C2 channels using entropy analysis, query volume anomalies, and subdomain length detection in SIEM platforms. Use when SOC teams need to identify DNS-based threats that bypass traditional network security…

plurigrid/asi · 73 tokens

analyzing-dns-logs-for-exfiltration

Analyzes DNS query logs to detect data exfiltration via DNS tunneling, DGA domain communication, and covert C2 channels using entropy analysis, query volume anomalies, and subdomain length detection in SIEM platforms. Use when SOC teams need to identify DNS-based threats that bypass traditional network security…

pinkpixel-dev/skills-collection-1 · 73 tokens