exploiting-active-directory-with-bloodhound

Maps Active Directory attack paths to Domain Admin using BloodHound graph analysis.

954|172|Updated Mar 13, 2026
One-click install
npx skills add https://github.com/xalgord/xalgorix --skill exploiting-active-directory-with-bloodhound
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: exploiting-active-directory-with-bloodhound
Source: https://github.com/xalgord/xalgorix/tree/main/internal/tools/skills/data/red-teaming/exploiting-active-directory-with-bloodhound
Command: npx skills add https://github.com/xalgord/xalgorix --skill exploiting-active-directory-with-bloodhound

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

During authorized red team engagements, manually tracing privilege escalation chains through Active Directory ACLs, group memberships, sessions, and delegations is slow and error-prone. This Skill guides the collection of AD relationship data with SharpHound or BloodHound.py and the graph-based analysis needed to reveal hidden attack paths from compromised accounts to high-value targets like Domain Admins.

Core Features & Use Cases

  • AD Data Collection: Structured workflow for running SharpHound or BloodHound.py collectors across single and multi-domain environments, including looped session collection.
  • Attack Path Analysis: Predefined and custom Cypher queries to find shortest paths to Domain Admins, Kerberoastable and AS-REP roastable accounts, DCSync rights, and ACL abuse edges such as GenericAll, WriteDACL, and AddKeyCredentialLink.
  • Exploitation Planning: Prioritization of attack chains with OPSEC considerations, MITRE ATT&CK mapping (T1087.002, T1069.002, T1482, and others), and validation checklists.
  • Use Case: During an authorized internal penetration test, an operator compromises a standard user account, collects AD data with SharpHound, marks the account as Owned in BloodHound, and discovers a ForceChangePassword edge chain leading to Domain Admin, which is then verified hop by hop and documented for the report.

Quick Start

Use this skill to plan a BloodHound collection and analysis workflow that finds attack paths from my compromised test account to Domain Admins in the lab domain.

Frequently Asked Questions about exploiting-active-directory-with-bloodhound

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I find attack paths to Domain Admin with BloodHound?

Collect AD data with SharpHound or BloodHound.py, import it into BloodHound, mark compromised accounts as Owned, then run the Shortest Path from Owned Principals to Domain Admins query. Confirm each edge by executing the first hop, since a graph edge is a hypothesis, not proof.

What is the difference between SharpHound and BloodHound.py?

SharpHound is the official .NET collector run on Windows hosts, while BloodHound.py is a Python collector that runs from Linux or Windows over the network. Both gather AD objects, ACLs, sessions, and group memberships into ZIP files for BloodHound ingestion.

Why does BloodHound show no path from my owned account?

Missing paths usually come from stale or absent session data, unmarked Owned principals, or collecting only the current domain. Run looped session collection, flag compromised accounts as Owned, collect across trusts, and use custom Cypher for edges like AddKeyCredentialLink that built-in queries miss.

Which BloodHound edges can be abused for privilege escalation?

Commonly exploitable edges include GenericAll, GenericWrite, WriteDACL, ForceChangePassword, AddKeyCredentialLink, ReadGMSAPassword, and ReadLAPSPassword. Each edge requires a different exploitation primitive, so verify you can actually execute the specific abuse before relying on the path.

Is BloodHound legal to use against Active Directory?

BloodHound is legal only for authorized security testing, lab environments, and systems you own or have written permission to test. Unauthorized use against third-party networks may violate computer fraud laws, and this Skill is restricted to authorized engagements.