meltedinhex/analyst-ai-pack / skills/hunting-active-directory-attacks
hunting-active-directory-attacks
VerifiedHunts for Active Directory credential and replication attacks — DCSync, Golden/Silver Ticket, and DCShadow — by analyzing directory-service-access (4662), Kerberos TGS (4769), and logon (4624) events for replication abuse and forged-ticket anomalies. Activates for requests to hunt DCSync, detect golden/silver tickets, or find Active Directory replication abuse.
Hunting Active Directory Attacks
When to Use
- You have AD/domain-controller telemetry (Event IDs 4662, 4769, 4624) and want to detect DCSync replication abuse, Golden/Silver Ticket usage, and DCShadow.
- You are investigating credential-access and domain-persistence activity.
Do not use this for Kerberoasting/AS-REP roasting — those have a dedicated hunt. This focuses on replication abuse and forged-ticket anomalies.
Prerequisites
- Event ID 4662 (directory service access), 4769 (TGS requests), and 4624 (logons) with account and detail fields.
Workflow
Step 1: Hunt DCSync replication abuse
python scripts/analyst.py hunt events.csv
Flags 4662 events granting the replication rights GUIDs (DS-Replication-Get-Changes
1131f6aa-… / -All 1131f6ad-…) to non-DC accounts.
Step 2: Detect forged-ticket anomalies
Surface 4769 requests with anomalies consistent with Golden/Silver Tickets (RC4 where AES is expected, missing preceding 4768, or accounts that do not exist), and logons with mismatched ticket lifetimes.
Step 3: Confirm
Correlate the flagged account/host with whether it is a legitimate DC or replication service.
Step 4: Operationalize
Write a detection for replication-rights grants to non-DC principals.
Validation
- DCSync flags key on the replication GUIDs granted to non-DC accounts.
- Forged-ticket anomalies are based on encryption type / missing-AS-REQ evidence.
- Findings map to ATT&CK T1003.006 / T1558.001.
Pitfalls
- Legitimate DCs and Azure AD Connect perform replication — allow-list them.
- Golden Tickets can perfectly mimic valid TGS; rely on corroborating anomalies, not one signal.
- Incomplete auditing (4662 object-access auditing must be enabled) causing blind spots.
References
- See
references/api-reference.mdfor the hunter. - ATT&CK T1003.006 and Event 4662 (linked in frontmatter).
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| planning-and-task-breakdownaddyosmani/agent-skillsBreaks work into ordered tasks. Use when you have a spec or clear requirements and need to break work into implementable tasks. Use when a task feels too large to start, when you need to estimate scope, or when parallel work is possible. | Stars: 119k | Updated | Claude CodeCodex | Verified | Install |
| screenpipethedotmack/claude-memSearch screen and audio history recorded by Screenpipe and optionally save selected context into claude-mem. Use when the user asks to recall desktop activity, a meeting, or something seen in another app through Screenpipe. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |
| contact-widgetnexu-io/open-designSelf-contained floating chat widget with welcome screen, social links, meeting button, and message input. Single HTML file, zero dependencies. | Stars: 108k | Updated | Claude CodeCodex | Verified | Install |
| meeting-notesnexu-io/open-designMeeting notes page — title bar with attendees, agenda checklist, decisions block, action items table with owners + dates, and a "next meeting" footer. Use when the brief mentions "meeting notes", "minutes", "1:1 notes", "all-hands recap", or "会议纪要". | Stars: 108k | Updated | Claude CodeCodex | Verified | Install |