Skip to content
New

DeepSeek V4.1 Flash free for 7 days: 10M tokens a day after a top-up of $10 or more. Until Nov 30.

How it works
meltedinhex/hunting-active-directory-attacksDFIR and threat hunting

hunting-active-directory-attacks

⁨Hunts for Active Directory credential and replication attacks — DCSync, Golden/Silver⁩

v1.0.03 installs+3 in 7 days24 StarsApache-2.0synced 10 hours ago

Install

No NotHoly CLI yet? Install it first.

$ curl -fsSL https://notholy.com/install.sh | sh
$ notholy skills install meltedinhex/hunting-active-directory-attacks

Writes to ⁦~/.notholy/skills⁩ after checking the signature and the SHA-256.

SignatureSigned, ed25519
vkwBap773d…2lRYNyCw==The CLI checks the SHA-256 and the signature before it writes a file.
Packagebd357b84…67ada116
bd357b84afae…b0fe67ada1164 files · ⁦3.2 KB⁩
ScanMedium2 findings
  • Executable script shipped with the skillscripts/analyst.py
  • Links to outside domains
See the full scan
Sourcegithub.com/meltedinhex/analyst-ai-pack/tree/main/skills/hunting-active-directory-attacks@da7600a

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

bash
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.md for the hunter.
  • ATT&CK T1003.006 and Event 4662 (linked in frontmatter).

Files in this version

Permissions

PermissionDeclaredFound by the scan
Reads filesNoNo
Writes filesNoNo
Runs shell commandsYesYes
Uses the networkYesYes
Uses connectorsNoNo
Drives a browserNoNo

Scan findings

Reviewed on Nov 13, 2026

  1. MediumFile · Executable script shipped with the skillscripts/analyst.py
  2. InfoLink · Links to outside domains

A clean scan lowers the risk but does not prove a package is safe. Read what you install.

VersionPublishedCommitSHA-256SignaturePermission change
v1.0.0Nov 13, 2026da7600abd357b84Signed–

Ask anything your scope allows.

Create an account, add credits and ask the first question in the chat or the terminal.

  1. 1/3

    Create the account

    Individual or company. You can switch to a company later without losing balance or keys.

    IndividualCompany
  2. 2/3

    Add credits

    By card. Pay per token, no subscription.

    $5.00minimum deposit
  3. 3/3

    Ask

    In the chat, or install the CLI and run notholy login in your terminal.

    $ notholy login