AGENT SKILL

exploiting-active-directory-with-bloodhound

BloodHound is a graph-based Active Directory reconnaissance tool that uses graph theory to reveal hidden and unintended relationships within AD environments. Red teams use BloodHound to identify attac

License 许可
Apache-2.0
最近更新
2026-09-11
Stars
★ 0
Forks
0

01 前言 Front Matter

name
exploiting-active-directory-with-bloodhound
tags
[ "red-team", "adversary-simulation", "mitre-attack", "exploitation", "post-exploitation", "active-directory", "bloodhound" ]
author
mahipal
domain
cybersecurity
license
Apache-2.0
version
1.0
nist_csf
[ "ID.RA-01", "GV.OV-02", "DE.AE-07" ]
subdomain
red-teaming
description
BloodHound is a graph-based Active Directory reconnaissance tool that uses graph theory to reveal hidden and unintended relationships within AD environments. Red teams use BloodHound to identify attac
mitre_attack
[ "T1595", "T1190", "T1059", "T1078", "T1592" ]
d3fend_techniques
[ "Restore Access", "Password Authentication", "Biometric Authentication", "Strong Password Policy", "Restore User Account Access" ]

02 资源文件 7

03 SKILL.md 正文

Exploiting Active Directory with BloodHound

Legal Notice: This skill is for authorized security testing and educational purposes only. Unauthorized use against systems you do not own or have written permission to test is illegal and may violate computer fraud laws.

Overview

BloodHound is a graph-based Active Directory reconnaissance tool that uses graph theory to reveal hidden and unintended relationships within AD environments. Red teams use BloodHound to identify attack paths from compromised accounts to high-value targets such as Domain Admins, identifying privilege escalation chains that would be nearly impossible to find manually. SharpHound is the official data collector that gathers AD objects, relationships, ACLs, sessions, and group memberships.

When to Use

  • When performing authorized security testing that involves exploiting active directory with bloodhound
  • When analyzing malware samples or attack artifacts in a controlled environment
  • When conducting red team exercises or penetration testing engagements
  • When building detection capabilities based on offensive technique understanding

Prerequisites

  • Familiarity with red teaming concepts and tools
  • Access to a test or lab environment for safe execution
  • Python 3.8+ with required dependencies installed
  • Appropriate authorization for any testing activities

Objectives

  • Collect Active Directory relationship data using SharpHound or BloodHound.py
  • Visualize attack paths from compromised accounts to Domain Admin
  • Identify misconfigured ACLs, group memberships, and delegation settings
  • Discover shortest attack paths to high-value targets
  • Map Kerberos delegation configurations for abuse
  • Document all identified privilege escalation chains

MITRE ATT&CK Mapping

  • T1087.002 - Account Discovery: Domain Account
  • T1069.002 - Permission Groups Discovery: Domain Groups
  • T1482 - Domain Trust Discovery
  • T1615 - Group Policy Discovery
  • T1018 - Remote System Discovery
  • T1033 - System Owner/User Discovery
  • T1016 - System Network Configuration Discovery

Workflow

Phase 1: Data Collection with SharpHound

  1. Transfer SharpHound collector to compromised host
  2. Execute collection with appropriate method (All, DCOnly, Session, LoggedOn)
  3. Collect from all reachable domains if multi-domain environment
  4. Exfiltrate ZIP data files to analysis workstation
  5. Import data into BloodHound CE or Legacy

Phase 2: Attack Path Analysis

  1. Mark owned principals (compromised accounts)
  2. Query shortest path to Domain Admins
  3. Identify Kerberoastable accounts with admin privileges
  4. Find AS-REP Roastable accounts
  5. Analyze ACL-based attack paths (GenericAll, GenericWrite, WriteDACL, ForceChangePassword)
  6. Review GPO abuse opportunities

Phase 3: Exploitation Planning

  1. Prioritize attack paths by complexity and stealth
  2. Identify required tools for each step in the chain
  3. Plan OPSEC considerations for each technique
  4. Execute identified attack chain
  5. Document evidence at each step

Tools and Resources

Tool Purpose Platform
BloodHound CE Graph visualization and analysis Web-based
SharpHound AD data collection (.NET) Windows
BloodHound.py AD data collection (Python) Linux/Windows
Cypher queries Custom graph queries Neo4j/BloodHound
PlumHound Automated BloodHound reporting Python
Max (BloodHound) BloodHound automation Python

Key BloodHound Queries

Query Purpose
Shortest Path to Domain Admins Find fastest route to DA
Find Kerberoastable Users with Path to DA SPN accounts leading to DA
Find AS-REP Roastable Users Accounts without pre-auth
Shortest Path from Owned Principals Paths from compromised accounts
Find Computers with Unsupported OS Legacy systems for exploitation
Find Users with DCSync Rights Accounts that can replicate AD
Find GPOs that Modify Local Group Membership GPO-based privilege escalation

Validation Criteria

  • [ ] SharpHound data collected from all domains
  • [ ] Attack paths identified from owned accounts to DA
  • [ ] ACL-based attack paths documented
  • [ ] Kerberoastable and AS-REP roastable accounts identified
  • [ ] Exploitation plan created with prioritized paths
  • [ ] Evidence screenshots captured for report

04 同仓库更多 Skills

NeelakshSaxena
NeelakshSaxena/Vayu

runpodctl

Runpod CLI for managing GPU/CPU workloads from the terminal — pods, serverless endpoints, templates, network volumes, Hub deploys, models, SSH, and file transfer (send/receive). Use for terminal/CI/scripting, Hub browse/deploy, SSH setup, `doctor`, or when the Runpod MCP tools are not connected. For structured tool calls in an MCP-enabled session, prefer runpod-mcp.

★ 0
NeelakshSaxena
NeelakshSaxena/Vayu

runpod

Start here for any Runpod task — running GPU/CPU pods, deploying serverless endpoints, templates, network volumes, building images, or understanding how Runpod works. Routes to the right skill (runpod-mcp, runpodctl, flash, companion-clis, runpod-usage, runpod-templates, runpod-migrate) and indexes two dozen live-verified end-to-end examples (golden paths) — use it when the lane is unclear, and for any multi-step or provisioning task even when it is not.

★ 0
NeelakshSaxena
NeelakshSaxena/Vayu

runpod-usage

How Runpod works and how to work it — pods vs serverless, GPU/VRAM selection, storage, building a container, networking, plus the agentic pod development loop (provision → ssh-exec → set up → poll readiness) and on-pod install hygiene (uv/apt). Use to answer "how does X work", "which GPU", "how do I build a container", or "how do I stand up a workload on a pod". Guidance, not a tool — execute with runpodctl, runpod-mcp, or flash.

★ 0
NeelakshSaxena
NeelakshSaxena/Vayu

runpod-templates

Runpod's official prebuilt pod templates (ComfyUI, PyTorch, and others): what each image ships, which ports and paths it uses, how to pick one, how to pin a version, and what is missing on first boot. Use when a task says "run <X> on a pod" and an official template already covers it, instead of building an image — and when a user needs help with or wants to fix something about a Runpod template they are already running (won't boot, can't reach the UI, missing models, wrong CUDA line, broken ComfyUI workflow metadata on imported workflows): start here and route onward. Deploy with runpodctl or runpod-mcp; end-to-end walkthroughs live in the runpod router's golden paths.

★ 0
NeelakshSaxena
NeelakshSaxena/Vayu

runpod-migrate

Migrate a codebase from the Runpod GraphQL API or REST v1 to REST v2 — inventory which parts use which API version, rewrite the call sites, flag breaking changes, and verify. Use when someone asks to move to v2, asks what v2 would change, or asks which Runpod API their code is on. For managing infrastructure rather than migrating code, use runpod-mcp or runpodctl.

★ 0
NeelakshSaxena
NeelakshSaxena/Vayu

runpod-mcp

Manage Runpod infrastructure — pods, serverless endpoints, jobs, templates, network volumes, container-registry auth, GPU/CPU catalog, and billing — via the Runpod MCP server's structured tool calls. Use when the Runpod MCP tools (create-pod, list-endpoints, …) are connected in this session, or to connect them (hosted OAuth or local npx). Prefer this over runpodctl for plain infra CRUD when MCP is available; use runpodctl for the terminal, file transfer, or SSH setup.

★ 0