Siem Logging
ancoleman/ai-design-components
Configure security information and event management (SIEM) systems for threat detection, log aggregation, and compliance.
Hunts for DNS-based persistence mechanisms such as DNS hijacking, dangling CNAME records enabling subdomain takeover, wildcard DNS abuse, and unauthorized zone or NS delegation changes, using…
Install Hunting For DNS Based Persistence
$ npx skills add mukul975/Anthropic-Cybersecurity-Skills --skill hunting-for-dns-based-persistence -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install mukul975/Anthropic-Cybersecurity-Skills hunting-for-dns-based-persistence --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/mukul975/Anthropic-Cybersecurity-Skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/hunting-for-dns-based-persistence .claude/skills/hunting-for-dns-based-persistence && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "hunting-for-dns-based-persistence" agent skill from https://github.com/mukul975/Anthropic-Cybersecurity-Skills/tree/main/skills/hunting-for-dns-based-persistence into .claude/skills/hunting-for-dns-based-persistence/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "hunting-for-dns-based-persistence", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/mukul975/Anthropic-Cybersecurity-Skills/tree/main/skills/hunting-for-dns-based-persistenceType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add mukul975/Anthropic-Cybersecurity-Skills --skill hunting-for-dns-based-persistence -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install mukul975/Anthropic-Cybersecurity-Skills hunting-for-dns-based-persistence --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mukul975/Anthropic-Cybersecurity-Skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/hunting-for-dns-based-persistence .agents/skills/hunting-for-dns-based-persistence && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "hunting-for-dns-based-persistence" agent skill from https://github.com/mukul975/Anthropic-Cybersecurity-Skills/tree/main/skills/hunting-for-dns-based-persistence into .agents/skills/hunting-for-dns-based-persistence/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "hunting-for-dns-based-persistence", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add mukul975/Anthropic-Cybersecurity-Skills --skill hunting-for-dns-based-persistence -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install mukul975/Anthropic-Cybersecurity-Skills hunting-for-dns-based-persistence --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mukul975/Anthropic-Cybersecurity-Skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/hunting-for-dns-based-persistence .cursor/skills/hunting-for-dns-based-persistence && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "hunting-for-dns-based-persistence" agent skill from https://github.com/mukul975/Anthropic-Cybersecurity-Skills/tree/main/skills/hunting-for-dns-based-persistence into .cursor/skills/hunting-for-dns-based-persistence/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "hunting-for-dns-based-persistence", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/mukul975/Anthropic-Cybersecurity-Skills.git --path skills/hunting-for-dns-based-persistence--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add mukul975/Anthropic-Cybersecurity-Skills --skill hunting-for-dns-based-persistence -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install mukul975/Anthropic-Cybersecurity-Skills hunting-for-dns-based-persistence --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mukul975/Anthropic-Cybersecurity-Skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/hunting-for-dns-based-persistence .gemini/skills/hunting-for-dns-based-persistence && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "hunting-for-dns-based-persistence" agent skill from https://github.com/mukul975/Anthropic-Cybersecurity-Skills/tree/main/skills/hunting-for-dns-based-persistence into .gemini/skills/hunting-for-dns-based-persistence/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "hunting-for-dns-based-persistence", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install mukul975/Anthropic-Cybersecurity-Skills hunting-for-dns-based-persistenceInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add mukul975/Anthropic-Cybersecurity-Skills --skill hunting-for-dns-based-persistence -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/mukul975/Anthropic-Cybersecurity-Skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/hunting-for-dns-based-persistence .github/skills/hunting-for-dns-based-persistence && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "hunting-for-dns-based-persistence" agent skill from https://github.com/mukul975/Anthropic-Cybersecurity-Skills/tree/main/skills/hunting-for-dns-based-persistence into .github/skills/hunting-for-dns-based-persistence/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "hunting-for-dns-based-persistence", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add mukul975/Anthropic-Cybersecurity-Skills --skill hunting-for-dns-based-persistence -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install mukul975/Anthropic-Cybersecurity-Skills hunting-for-dns-based-persistence --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mukul975/Anthropic-Cybersecurity-Skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/hunting-for-dns-based-persistence .opencode/skills/hunting-for-dns-based-persistence && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "hunting-for-dns-based-persistence" agent skill from https://github.com/mukul975/Anthropic-Cybersecurity-Skills/tree/main/skills/hunting-for-dns-based-persistence into .opencode/skills/hunting-for-dns-based-persistence/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "hunting-for-dns-based-persistence", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
hunting-for-dns-based-persistence- GitHub stars
- 34k
- Token cost
- ~790 tokens
- SKILL.md length
- 291 words
- Files
- 4 (incl. scripts, references)
- Skills in repo
- 644
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Hunts for DNS-based persistence mechanisms such as DNS hijacking, dangling CNAME records enabling subdomain takeover, wildcard DNS abuse, and unauthorized zone or NS delegation changes, using…
- Works in 4 steps: Baseline DNS Records → Query Passive DNS History → Detect Anomalies → …
- Investigating suspected DNS hijacking
- SKILL.md covers Overview, When to Use, Prerequisites and Steps, plus 1 more section
- Runs Python scripts from its folder
What it does
Hunting For DNS Based Persistence is an agent skill from mukul975/Anthropic-Cybersecurity-Skills. Hunts for DNS-based persistence mechanisms such as DNS hijacking, dangling CNAME records enabling subdomain takeover, wildcard DNS abuse, and unauthorized zone or NS delegation changes, using passive DNS history (SecurityTrails API), Route53/Azure DNS/Cloudflare audit logs, and zone transfer analysis. Use when investigating suspected DNS hijacking or subdomain takeover, or when threat hunting for DNS record tampering that persists across credential rotations and endpoint reimaging.
Its SKILL.md is about 790 tokens, which your agent loads only when the skill is triggered. The skill folder holds 5 other files, including scripts and reference files (for example `references/api-reference.md` and `scripts/agent.py`).
It sits in Security, covering Security operations. It works with Cloudflare and Microsoft Azure. The repository describes itself as: 817 structured cybersecurity skills for AI agents · Mapped to 6 frameworks: MITRE ATT&CK, NIST CSF 2.0, MITRE ATLAS, D3FEND, NIST AI RMF & MITRE F3 (Fight Fraud) · agentskills.io…. The licence is Apache-2.0.
When your agent uses it
- Investigating suspected DNS hijacking
- Subdomain takeover
- Threat hunting for DNS record tampering that persists across credential rotations and endpoint reimaging
Example prompts
- “Use the hunting-for-dns-based-persistence skill to hunt for DNS-based persistence mechanisms such as DNS hijacking, dangling CNAME records enabling…”
- “/hunting-for-dns-based-persistence”
Requirements
- Python 3
Workflow steps
4 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 54a7988. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Ships 1 file in scripts/ (Python), which the agent can run.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Hunting For DNS Based Persistence loads about 790 tokens when it runs, and up to ~1.5k if it reads all its reference files. Until then it costs about 130 tokens; SKILL.md has 291 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.
SKILL.md
The full file from mukul975/Anthropic-Cybersecurity-Skills at commit 54a7988, republished under its Apache-2.0 licence (© mukul975). 291 words, ~790 tokens.
Download SKILL.mdSave it as
.claude/skills/hunting-for-dns-based-persistence/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.- name
- hunting-for-dns-based-persistence
- description
- Hunts for DNS-based persistence mechanisms such as DNS hijacking, dangling CNAME records enabling subdomain takeover, wildcard DNS abuse, and unauthorized zone or NS delegation changes, using passive DNS history (SecurityTrails API), Route53/Azure DNS/Cloudflare audit logs, and zone transfer analysis. Use when investigating suspected DNS hijacking or subdomain takeover, or when threat hunting for DNS record tampering that persists across credential rotations and endpoint reimaging.
- domain
- cybersecurity
- subdomain
- threat-hunting
- tags
- dns, persistence, threat-hunting, passive-dns, dns-hijacking, subdomain-takeover, securitytrails
- version
- 1.0
- author
- mahipal
- license
- Apache-2.0
- nist_csf
- DE.CM-01, DE.AE-02, DE.AE-07, ID.RA-05
- mitre_attack
- T1046, T1057, T1082, T1083, T1547
Hunting for DNS-based Persistence
Overview
Attackers establish DNS-based persistence by hijacking DNS records, creating unauthorized subdomains, abusing wildcard DNS entries, or modifying NS delegations to redirect traffic through attacker-controlled infrastructure. These techniques survive credential rotations, endpoint reimaging, and traditional remediation because DNS changes persist independently of compromised hosts. Detection requires passive DNS historical analysis, zone file auditing, and monitoring for unauthorized record modifications. This skill covers hunting methodologies using SecurityTrails passive DNS API, DNS audit logs from Route53/Azure DNS/Cloudflare, and zone transfer analysis.
When to Use
- When investigating security incidents that require hunting for dns based persistence
- When building detection rules or threat hunting queries for this domain
- When SOC analysts need structured procedures for this analysis type
- When validating security monitoring coverage for related attack techniques
Prerequisites
- SecurityTrails API key (free tier provides 50 queries/month)
- Access to DNS provider audit logs (Route53, Azure DNS, Cloudflare, or on-premises DNS)
- Python 3.9+ with requests library
- DNS zone file access or AXFR capability for internal zones
- Historical DNS baseline for comparison
Steps
Step 1: Baseline DNS Records
Export current DNS zone records and establish baseline for all authorized A, AAAA, CNAME, MX, NS, and TXT records.
Step 2: Query Passive DNS History
Use SecurityTrails API to retrieve historical DNS records and identify unauthorized changes, new subdomains, and CNAME records pointing to decommissioned services (dangling CNAMEs).
Step 3: Detect Anomalies
Compare current records against baseline to identify unauthorized modifications, wildcard records that resolve all subdomains, NS delegation changes, and MX record hijacking.
Step 4: Investigate Findings
Correlate DNS anomalies with threat intelligence feeds, check resolution targets against known malicious infrastructure, and validate record ownership.
Expected Output
JSON report listing DNS anomalies with record type, historical changes, risk severity, and remediation recommendations for each finding.
© mukul975, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 3 other files (scripts, references) in skills/hunting-for-dns-based-persistence of mukul975/Anthropic-Cybersecurity-Skills.
- SKILL.md
- LICENSE
- references/api-reference.md
- scripts/agent.py
Open the folder on GitHubat commit 54a7988
Compare with similar skills
Hunting For DNS Based Persistence next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Hunting For DNS Based Persistence this skillmukul975/Anthropic-Cybersecurity-Skills | 34k | — | ~790 | Automated safety check: Pass | Apache-2.0 | |
| Siem Loggingancoleman/ai-design-components | 525 | — | ~3.4k | Automated safety check: Pass | MIT | |
| External Enumerationforefy/.context | 152 | — | ~3.1k | Automated safety check: Pass | MIT | |
| Cloud Defensetransilienceai/communitytools | 563 | — | ~476 | Automated safety check: Pass | MIT | |
| Investigating GCP Incidentstrilwu/secskills | 157 | — | ~2.2k | Automated safety check: Pass | MIT | |
| Defender For Cloud Hardeningvinayaklatthe/microsoft-security-skills | 175 | — | ~1.9k | Automated safety check: Pass | MIT |
Similar skills
External Enumeration
forefy/.context
Passively map a company's domains, subdomains, DNS ownership, tech stack, and CDNs.
Cloud Defense
transilienceai/communitytools
Detect and break the cloud post-compromise attack chain (AWS / Azure / GCP) — per-stage CloudTrail / Activity-Log / Audit-Log detection signals and the preventive controls that close each step.
Investigating GCP Incidents
trilwu/secskills
Investigate a security incident in Google Cloud — establishing what audit logging exists before trusting a gap, reconstructing activity from Cloud Audit Logs, triaging service-account and OAuth…
Defender For Cloud Hardening
vinayaklatthe/microsoft-security-skills
Guidance for Microsoft Defender for Cloud — cloud security posture management (CSPM) and cloud workload protection (CWPP) across Azure, AWS, and GCP.
Sentinel
vinayaklatthe/microsoft-security-skills
Guidance for designing and operating Microsoft Sentinel, the cloud-native SIEM and SOAR delivered through the Defender portal.
More from mukul975/Anthropic-Cybersecurity-Skills
All 644 skills in this repoCampaign Attribution Evidence Analysis
mukul975/Anthropic-Cybersecurity-Skills
Weighs infrastructure, TTP, malware code and timing evidence with the Diamond Model and competing hypotheses to reach a confidence-rated attribution.
Go Malware Analysis in Ghidra
mukul975/Anthropic-Cybersecurity-Skills
Walks through reverse engineering Go-compiled malware in Ghidra: parsing buildinfo and pclntab, recovering stripped function names and extracting dependencies.
LNK and Jump List Forensics
mukul975/Anthropic-Cybersecurity-Skills
Guides forensic analysis of Windows LNK shortcut files and Jump Lists with LECmd, JLECmd and manual parsing to show file access and program execution.
Malware Persistence Analysis with Autoruns
mukul975/Anthropic-Cybersecurity-Skills
Hunts Windows malware persistence with Sysinternals Autoruns, covering run keys, services, scheduled tasks and drivers, with baseline comparison.
NTFS MFT Deleted File Recovery
mukul975/Anthropic-Cybersecurity-Skills
Guides a Windows forensic examination of the NTFS Master File Table to recover deleted-file evidence, build timelines and spot timestomping.
Network Covert Channel Analysis
mukul975/Anthropic-Cybersecurity-Skills
Detects DNS tunneling, ICMP exfiltration and HTTP-based covert channels in packet captures and DNS logs when hunting for hidden command-and-control traffic.
Related
Works with
Categories
Questions about Hunting For DNS Based Persistence
What does Hunting For DNS Based Persistence do?
Hunts for DNS-based persistence mechanisms such as DNS hijacking, dangling CNAME records enabling subdomain takeover, wildcard DNS abuse, and unauthorized zone or NS delegation changes, using…. Hunting For DNS Based Persistence is an agent skill from mukul975/Anthropic-Cybersecurity-Skills. Hunts for DNS-based persistence mechanisms such as DNS hijacking, dangling CNAME records enabling subdomain takeover, wildcard DNS abuse, and unauthorized zone or NS delegation changes, using passive DNS history (SecurityTrails API), Route53/Azure DNS/Cloudflare audit logs, and zone transfer analysis.
When should I use Hunting For DNS Based Persistence?
Hunting For DNS Based Persistence fits situations like: investigating suspected DNS hijacking; subdomain takeover; threat hunting for DNS record tampering that persists across credential rotations and endpoint reimaging.
How do I install Hunting For DNS Based Persistence in Claude Code?
Run `npx skills add mukul975/Anthropic-Cybersecurity-Skills --skill hunting-for-dns-based-persistence -a claude-code`. Or copy the skill folder (skills/hunting-for-dns-based-persistence in mukul975/Anthropic-Cybersecurity-Skills) into .claude/skills/hunting-for-dns-based-persistence in your project. Claude Code loads it when a task matches its description.
How do I install Hunting For DNS Based Persistence in Codex?
Run `npx skills add mukul975/Anthropic-Cybersecurity-Skills --skill hunting-for-dns-based-persistence -a codex`. Or copy the skill folder (skills/hunting-for-dns-based-persistence in mukul975/Anthropic-Cybersecurity-Skills) into .agents/skills/hunting-for-dns-based-persistence in your project. Codex loads it when a task matches its description.
Can I use Hunting For DNS Based Persistence in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add mukul975/Anthropic-Cybersecurity-Skills --skill hunting-for-dns-based-persistence -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/hunting-for-dns-based-persistence, .gemini/skills/hunting-for-dns-based-persistence, .github/skills/hunting-for-dns-based-persistence and .opencode/skills/hunting-for-dns-based-persistence in your project.
What does Hunting For DNS Based Persistence need to run?
Going by SKILL.md and its folder, Hunting For DNS Based Persistence needs Python for the scripts in its folder. Our summary lists: Python 3.
Does Hunting For DNS Based Persistence access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Hunting For DNS Based Persistence safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
What licence does Hunting For DNS Based Persistence use?
Hunting For DNS Based Persistence is published under the Apache-2.0 licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Hunting For DNS Based Persistence use?
About 790 tokens (SKILL.md is roughly 3.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 665 tokens, read only when the agent opens those files.
What are the alternatives to Hunting For DNS Based Persistence?
Skills that share tags, products or a category with Hunting For DNS Based Persistence: Siem Logging (ancoleman/ai-design-components, 525 stars), External Enumeration (forefy/.context, 152 stars), Cloud Defense (transilienceai/communitytools, 563 stars) and Investigating GCP Incidents (trilwu/secskills, 157 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Hunting For DNS Based Persistence?
mukul975 (a GitHub user) maintains it in mukul975/Anthropic-Cybersecurity-Skills, which has 34,116 GitHub stars. The repository holds 644 skills in this directory. The repository was last updated on August 31, 2026.
Source: mukul975/Anthropic-Cybersecurity-Skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.