hunting-for-dcsync-attacks

Detect DCSync attacks by analyzing Windows Event ID 4662 for unauthorized DS-Replication-Get-Changes requests from non-domain-controller accounts.

Works with

Claude CodeCursorClineWindsurfCodexGooseGitHub CopilotZed

0

total installs

0

this week

8.6K

GitHub stars

0

upvotes

Install Skill

Run in your terminal

$npx skills install mukul975/Anthropic-Cybersecurity-Skills/hunting-for-dcsync-attacks

0

installs

0

this week

8.6K

stars

Installation Guide

How to use hunting-for-dcsync-attacks on Cursor

AI-first code editor with Composer

1

Prerequisites

Before installing skills in Cursor, ensure your development environment meets these requirements:

  • Cursor installed and configured on your machine
  • Node.js 16+ with npm — verify with node --version
  • Active project directory where you want to add hunting-for-dcsync-attacks
2

Run the install command

Execute the skills CLI command in your project's root directory to begin installation:

$npx skills install mukul975/Anthropic-Cybersecurity-Skills/hunting-for-dcsync-attacks

Fetches hunting-for-dcsync-attacks from mukul975/Anthropic-Cybersecurity-Skills and configures it for Cursor.

3

Select Cursor when prompted

The CLI shows a list of agents. Use arrow keys and space to select Cursor:

◆ Which agents do you want to install to?
│ ── Universal (.agents/skills) ────────────────
│ · Cline · Codex · Goose · Windsurf
│ ●Cursor(selected)
│ · Cursor · Aider · Continue
4

Verify installation

Confirm successful installation by checking the skill directory location:

.cursor/skills/hunting-for-dcsync-attacks

Restart Cursor to activate hunting-for-dcsync-attacks. Access via /hunting-for-dcsync-attacks in your agent's command palette.

Security Notice

We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.

Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.

Documentation

name
hunting-for-dcsync-attacks
description
Detect DCSync attacks by analyzing Windows Event ID 4662 for unauthorized DS-Replication-Get-Changes requests from non-domain-controller accounts.
domain
cybersecurity
subdomain
threat-hunting
tags
- threat-hunting - dcsync - active-directory - credential-access - t1003.006 - mimikatz - windows - dfir
version
'1.0'
author
mahipal
license
Apache-2.0
d3fend_techniques
- Application Protocol Command Analysis - Network Isolation - Network Traffic Analysis - Client-server Payload Profiling - Platform Monitoring
nist_csf
- DE.CM-01 - DE.AE-02 - DE.AE-07 - ID.RA-05

Hunting for DCSync Attacks

When to Use

  • When hunting for DCSync credential theft (MITRE ATT&CK T1003.006)
  • After detecting Mimikatz or similar tools in the environment
  • During incident response involving Active Directory compromise
  • When monitoring for unauthorized domain replication requests
  • During purple team exercises testing AD attack detection

Prerequisites

  • Windows Security Event Log forwarding enabled (Event ID 4662)
  • Audit Directory Service Access enabled via Group Policy
  • Domain Computers SACL configured on Domain Object for machine account detection
  • SIEM with Windows event data ingested (Splunk, Elastic, Sentinel)
  • Knowledge of legitimate domain controller accounts and replication partners

Workflow

  1. Enable Auditing: Ensure Audit Directory Service Access is enabled on domain controllers.
  2. Collect Events: Gather Windows Event ID 4662 with AccessMask 0x100 (Control Access).
  3. Filter Replication GUIDs: Search for DS-Replication-Get-Changes and DS-Replication-Get-Changes-All.
  4. Identify Non-DC Sources: Flag events where SubjectUserName is not a domain controller machine account.
  5. Correlate with Network: Cross-reference source IPs against known DC addresses.
  6. Validate Findings: Exclude legitimate replication tools (Azure AD Connect, SCCM).
  7. Respond: Disable compromised accounts, reset krbtgt, investigate lateral movement.

Key Concepts

ConceptDescription
DCSyncTechnique abusing AD replication protocol to extract password hashes
Event ID 4662Directory Service Access audit event
DS-Replication-Get-ChangesGUID 1131f6aa-9c07-11d1-f79f-00c04fc2dcd2
DS-Replication-Get-Changes-AllGUID 1131f6ad-9c07-11d1-f79f-00c04fc2dcd2
AccessMask 0x100Control Access right indicating extended rights verification
T1003.006OS Credential Dumping: DCSync

Tools & Systems

ToolPurpose
Windows Event ViewerDirect event log analysis
SplunkSIEM correlation of Event 4662
Elastic SecurityDetection rules for DCSync patterns
Mimikatz lsadump::dcsyncAttack tool used to perform DCSync
Impacket secretsdump.pyPython-based DCSync implementation
BloodHoundIdentify accounts with replication rights

Output Format

Hunt ID: TH-DCSYNC-[DATE]-[SEQ]
Technique: T1003.006
Domain Controller: [DC hostname]
Subject Account: [Account performing replication]
Source IP: [Non-DC IP address]
GUID Accessed: [Replication GUID]
Risk Level: [Critical/High/Medium/Low]
Recommended Action: [Disable account, reset krbtgt, investigate]

List & Monetize Your Skill

Submit your Claude Code skill and start earning

Get started →

Use Cases

Task Automation & Efficiency

Automate repetitive workflows and reduce manual effort

Example

Generate reports, summarize documents, draft communications

Save 3-5 hours per week on routine tasks

Knowledge Enhancement

Learn new skills, understand complex topics, get expert guidance

Example

Explain concepts, provide examples, suggest learning resources

Accelerate learning and skill development by 2x

Quality Improvement

Enhance output quality through reviews, suggestions, and refinements

Example

Review drafts, suggest improvements, catch errors

Improve work quality by 30-40% with less effort

Implementation Guide

Prerequisites

  • Claude Desktop or compatible AI client with skill support
  • Clear understanding of task or problem to solve
  • Willingness to iterate and refine outputs

Time Estimate

15-45 minutes depending on use case complexity

Steps

  1. 1Install skill using provided installation command
  2. 2Test with simple use case relevant to your work
  3. 3Evaluate output quality and relevance
  4. 4Iterate on prompts to improve results
  5. 5Integrate into regular workflow if valuable

Common Pitfalls

  • Expecting perfect results without iteration
  • Not providing enough context in prompts
  • Using skill for tasks outside its intended scope
  • Accepting outputs without review and validation

Best Practices

✓ Do

  • +Start with clear, specific prompts
  • +Provide relevant context and constraints
  • +Review and refine all outputs before using
  • +Iterate to improve output quality
  • +Document successful prompt patterns

✗ Don't

  • Don't use without understanding skill limitations
  • Don't skip validation of outputs
  • Don't share sensitive information in prompts
  • Don't expect skill to replace human judgment

💡 Pro Tips

  • Be specific about desired format and style
  • Ask for multiple options to choose from
  • Request explanations to understand reasoning
  • Combine AI efficiency with human expertise

When to Use This

✓ 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.

Learning Path

  1. 1Familiarize yourself with skill capabilities and limitations
  2. 2Start with low-risk, non-critical tasks
  3. 3Progress to more complex and valuable use cases
  4. 4Build expertise through regular use and experimentation

Related Skills

Reviews

4.771 reviews
  • K
    Kwame ZhangDec 24, 2024

    hunting-for-dcsync-attacks has been reliable in day-to-day use. Documentation quality is above average for community skills.

  • G
    Ganesh MohaneDec 20, 2024

    We added hunting-for-dcsync-attacks from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

  • K
    Kwame ChenDec 20, 2024

    hunting-for-dcsync-attacks has been reliable in day-to-day use. Documentation quality is above average for community skills.

  • E
    Emma TandonDec 16, 2024

    I recommend hunting-for-dcsync-attacks for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.

  • M
    Mia FarahDec 12, 2024

    Useful defaults in hunting-for-dcsync-attacks — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • J
    James LiDec 8, 2024

    hunting-for-dcsync-attacks fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

  • A
    Ama HuangNov 27, 2024

    Registry listing for hunting-for-dcsync-attacks matched our evaluation — installs cleanly and behaves as described in the markdown.

  • O
    Omar KapoorNov 15, 2024

    hunting-for-dcsync-attacks reduced setup friction for our internal harness; good balance of opinion and flexibility.

  • K
    Kabir ChoiNov 15, 2024

    We added hunting-for-dcsync-attacks from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

  • A
    Ama GhoshNov 11, 2024

    Solid pick for teams standardizing on skills: hunting-for-dcsync-attacks is focused, and the summary matches what you get after install.

showing 1-10 of 71

1 / 8

Discussion

Comments — not star reviews
  • No comments yet — start the thread.