Claude-AD README

The project's README from github.com/ADScanPro/Claude-AD. As one markdown file: README.md.

Claude-AD

Active Directory pentest methodology for Claude Code.

License: MIT Claude Code plugin Version Techniques

Skills, agents and commands that give Claude the playbook for an internal Active Directory assessment: the phase order, the environment constraints that break your tooling, the telemetry each technique leaves behind, and how a finding maps to a compliance control. It drives standard tooling (netexec, impacket, certipy, bloodyAD, BloodHound CE). You still run the engagement; Claude carries the method.

What this is

Every AD assessment follows the same spine: map before you exploit, harvest the easy credentials before you spray, collect the graph before you reason about paths. That spine, plus the hundred small constraints a hardened domain throws at you (NTLM disabled, AES-only Kerberos, LDAP channel binding, SPNs that must be FQDNs), is what separates an operator who finishes the engagement from one who spends a day debugging invalidCredentials.

Claude-AD encodes that method as Claude Code skills so Claude runs the standard tools in the right order, reads the environment correctly, and tells you what each step will look like to a defender.

It covers:

It orchestrates third-party tools. BloodHound CE (Apache-2.0), impacket, certipy, netexec and bloodyAD do the work; Claude-AD is the method that drives them.

Install

Claude-AD is a Claude Code plugin. From inside Claude Code:

/plugin marketplace add ADScanPro/Claude-AD
/plugin install claude-ad@claude-ad

The first line registers this repo as a marketplace; the second installs the plugin. Once installed, the skills load automatically when you work on an AD engagement, and the commands (/ad-scope, /ad-recon, /ad-attack-paths) are available.

Layout

Claude-AD/
├── skills/
│   ├── ad-methodology/          # phase order and why
│   ├── ad-environment-constraints/  # what breaks your tooling in a hardened domain
│   ├── ad-opsec-telemetry/      # Event IDs and MDI alerts per technique
│   ├── kerberos-attacks/        # Kerberoasting, AS-REP, delegation
│   ├── adcs-attacks/            # ESC1-ESC17 with certipy
│   ├── acl-abuse/               # GenericAll, WriteDACL, replication rights
│   ├── coercion-ntlm-relay/     # PetitPotam/PrinterBug/DFSCoerce + ntlmrelayx
│   └── compliance-mapping/      # conceptual technique -> DORA/NIS2/ENS control
├── agents/
│   ├── ad-enumerator.md         # runs collection with standard tooling
│   ├── ad-attack-planner.md     # reasons low-priv -> Domain Admin paths
│   └── ad-exploit-operator.md   # executes one step, with a human gate
└── commands/
    ├── ad-scope.md
    ├── ad-recon.md
    └── ad-attack-paths.md

Scope and ethics

This is for authorized engagements only: your own lab, a domain you are contracted to test, a CTF. The exploitation agents ask for confirmation before any action that modifies the directory (a password reset, a group add, an RBCD write), and note where rollback applies. Use it where you have permission to.

Where Claude-AD ends and ADscan begins

Claude-AD gives you the method. It tells Claude what to run, in what order, what each technique looks like on the wire, and which compliance control it touches. You still drive every tool by hand and read every result yourself.

ADscan is the engine. It runs the whole chain from a low-privilege user to Domain Admin on its own, on-prem, with guardrails and rollback, and turns the result into a report with control IDs a DORA, NIS2 or ENS auditor will accept. Where this repo hands Claude the playbook, ADscan is the tool that executes it end to end and writes the evidence.

ADscan is free and source-available. If the manual method here is useful and you want it run and mapped for you, that is what it is for.

Prior art and references

Claude-AD stands on the shoulders of the community. The techniques it encodes are documented in depth at The Hacker Recipes, the reference every skill here points back to for exact syntax. It sits alongside the growing set of Claude Code security collections (Claude-OSINT, Claude-BugHunter, claude-pentest), filling the Active-Directory-internal gap those bundles leave open. The tooling it drives (BloodHound CE, impacket, certipy, netexec, bloodyAD) is the work of their respective authors.

Contributing

New techniques, sharper detection guidance, corrections to the compliance mapping: open an issue or a PR. Keep it AD-internal and keep the commands real.

License

MIT. See LICENSE. ADscan itself is a separate product under the Business Source License 1.1 (source-available).

Keywords: Active Directory penetration testing · Claude Code skills · red team · Kerberoasting · AS-REP roasting · ADCS ESC1-ESC17 · DCSync · ACL abuse · NTLM relay & coercion (PetitPotam, PrinterBug, DFSCoerce) · Kerberos delegation · BloodHound CE attack paths · OPSEC & MDI telemetry · DORA / NIS2 / ENS compliance mapping · netexec · impacket · certipy · bloodyAD.

Claude-AD (ADScanPro/Claude-AD)

compliance
Searching Database…

212 ·GitHub
Claude-AD
What is this?Claude-AD is a Claude Code plugin that gives Claude the methodology for an internal Active Directory penetration test: skills, agents and slash commands covering Kerberoasting, ADCS ESC1-17, DCSync, ACL abuse, NTLM relay and delegation abuse, each with OPSEC and telemetry notes.
Is this a scanning tool itself, or something that tells Claude what to run?It is not a scanner — it is a methodology encoded as Claude Code skills. Claude tells you the phase order and the right command, but you still run netexec, impacket, certipy, bloodyAD and BloodHound CE yourself and read the results.
What tools do I need already set up to actually run the attacks?You need the standard AD pentest toolkit installed yourself: netexec, impacket, certipy, bloodyAD and BloodHound CE. Claude-AD does not bundle or replace them, it just tells you which one to run and how.
Does this automate the actual attack chain for me?No, Claude-AD only gives the method: order of operations, OPSEC notes, detection events. Running the chain end-to-end from a low-privilege user to Domain Admin automatically is a separate product called ADscan.
Where does this run?It runs wherever Claude Code runs, so macOS, Linux and Windows, since it is installed as a Claude Code plugin rather than a standalone application.
Is the license the same across the whole project?This repository is MIT licensed, but the related full-automation product ADscan is a separate tool under the Business Source License 1.1 (source-available), not MIT.
What AD attack techniques does it cover?Kerberoasting and AS-REP roasting, ADCS ESC1 through ESC17, ACL abuse (GenericAll/WriteDACL/replication rights), coercion and NTLM relay (PetitPotam, PrinterBug, DFSCoerce), and Kerberos delegation abuse.
What is the compliance mapping feature for?Each technique is conceptually mapped to the control family it touches under DORA, NIS2 and ENS regulations, turning a technical finding into an audit-ready compliance note.
Does it stop me from accidentally breaking things in the domain?Yes, the exploitation agents ask for confirmation before any directory-modifying action like a password reset, group add or RBCD write, and note where rollback applies.
What is the difference between this repo and ADscan?Claude-AD is the manual methodology you drive by hand; ADscan is a separate, source-available engine that executes the same attack chain end to end automatically and produces an auditor-ready report.
What are similar projects?Claude-Red, Decepticon, Anthropic-Cybersecurity-Skills, bug-bounty-hunting-prompts, dirsearch, evilginx2, CVE-2026-62911, nishang
Which topics is it in?pentest-tool, mitre-attack, ethical-hacking, redteam, compliance, security-research, infosec, claude-code-plugin, hacking-tool, offensive-security, red-team, pentesting
Creator
ADScanPro
Size
<0.1 MB
Stars
212
Updated
CommitAug 24
Age
1mo
Commits · 90 Days