Hunt for DNS-based persistence mechanisms including DNS hijacking, dangling CNAME records, wildcard DNS abuse, and unauthorized zone modifications using passive DNS databases, SecurityTrails API, and DNS audit log analysis.
Automate repetitive workflows and reduce manual effort
Example: Generate reports, summarize documents, draft communications
Save 3-5 hours per week on routine tasks
Learn new skills, understand complex topics, get expert guidance
Example: Explain concepts, provide examples, suggest learning resources
Accelerate learning and skill development by 2x
Enhance output quality through reviews, suggestions, and refinements
Example: Review drafts, suggest improvements, catch errors
Improve work quality by 30-40% with less effort
Time estimate: 15-45 minutes depending on use case complexity
Prerequisites
Submit your Claude Code skill and start earning
epx add mukul975/Anthropic-Cybersecurity-Skills/hunting-for-dns-based-persistenceCompatible with
Supported agents
| name | hunting-for-dns-based-persistence |
| description | Hunt for DNS-based persistence mechanisms including DNS hijacking, dangling CNAME records, wildcard DNS abuse, and unauthorized zone modifications using passive DNS databases, SecurityTrails API, and DNS audit log analysis. |
| 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 |
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.
Export current DNS zone records and establish baseline for all authorized A, AAAA, CNAME, MX, NS, and TXT records.
Use SecurityTrails API to retrieve historical DNS records and identify unauthorized changes, new subdomains, and CNAME records pointing to decommissioned services (dangling CNAMEs).
Compare current records against baseline to identify unauthorized modifications, wildcard records that resolve all subdomains, NS delegation changes, and MX record hijacking.
Correlate DNS anomalies with threat intelligence feeds, check resolution targets against known malicious infrastructure, and validate record ownership.
JSON report listing DNS anomalies with record type, historical changes, risk severity, and remediation recommendations for each finding.
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionhunting-for-dns-based-persistenceExecute the skills CLI command in your project's root directory to begin installation:
epx add mukul975/Anthropic-Cybersecurity-Skills/hunting-for-dns-based-persistenceFetches hunting-for-dns-based-persistence from mukul975/Anthropic-Cybersecurity-Skills and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
.cursor/skills/hunting-for-dns-based-persistence
Restart Cursor to activate hunting-for-dns-based-persistence. Access via /hunting-for-dns-based-persistencein your agent's command palette.
Learn more:View source on GitHubSkills CLI docsAbout CursorWhat are agent skills?
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.
✗ Avoid when
Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.
detecting-insider-threat-behaviors
mukul975/Anthropic-Cybersecurity-Skills · detecting-insider-threat-behaviors · same repo
analyzing-dns-logs-for-exfiltration
mukul975/Anthropic-Cybersecurity-Skills · analyzing-dns-logs-for-exfiltration · same repo
performing-thick-client-application-penetration-test
mukul975/Anthropic-Cybersecurity-Skills · performing-thick-client-application-penetration-test · same repo
generating-threat-intelligence-reports
mukul975/Anthropic-Cybersecurity-Skills · generating-threat-intelligence-reports · same repo
performing-subdomain-enumeration-with-subfinder
mukul975/Anthropic-Cybersecurity-Skills · performing-subdomain-enumeration-with-subfinder · same repo
mapping-mitre-attack-techniques
mukul975/Anthropic-Cybersecurity-Skills · mapping-mitre-attack-techniques · same repo
hunting-for-dns-based-persistence is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
We added hunting-for-dns-based-persistence from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
Solid pick for teams standardizing on skills: hunting-for-dns-based-persistence is focused, and the summary matches what you get after install.
Keeps context tight: hunting-for-dns-based-persistence is the kind of skill you can hand to a new teammate without a long onboarding doc.
hunting-for-dns-based-persistence fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
Registry listing for hunting-for-dns-based-persistence matched our evaluation — installs cleanly and behaves as described in the markdown.
Registry listing for hunting-for-dns-based-persistence matched our evaluation — installs cleanly and behaves as described in the markdown.
hunting-for-dns-based-persistence reduced setup friction for our internal harness; good balance of opinion and flexibility.
hunting-for-dns-based-persistence fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
I recommend hunting-for-dns-based-persistence for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
showing 1-10 of 68