[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7A6SCQB1W9ZBFD390Z1K16M":3,"skill-same:01M7A6SCQB1W9ZBFD390Z1K16M":108},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":16,"sourceHtmlUrl":17,"categories":18,"keywords":19,"publishedAt":20,"linkOnly":21,"markdownContent":22,"markdownBody":23,"frontMatter":24,"refName":53,"commitSha":54,"skillDirectory":55,"forksCount":14,"repositoryHtmlUrl":56,"repositoryHomepageUrl":6,"ownerHtmlUrl":57,"ownerBlogUrl":6,"ownerDescription":58,"updatedAt":59,"install":60,"resources":73},"01M7A6SCQB1W9ZBFD390Z1K16M","exploiting-active-directory-with-bloodhound",null,"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","NeelakshSaxena\u002FVayu","NeelakshSaxena","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F87892838?v=4","01M7A3B9YFS6F6N9DD1787DT86","Neelaksh Saxena","01M7A3B9ZKBT09MNMPX2XN69BY",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fexploiting-active-directory-with-bloodhound\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fexploiting-active-directory-with-bloodhound\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: exploiting-active-directory-with-bloodhound\ndescription: BloodHound is a graph-based Active Directory reconnaissance tool that\n  uses graph theory to reveal hidden and unintended relationships within AD environments.\n  Red teams use BloodHound to identify attac\ndomain: cybersecurity\nsubdomain: red-teaming\ntags:\n- red-team\n- adversary-simulation\n- mitre-attack\n- exploitation\n- post-exploitation\n- active-directory\n- bloodhound\nversion: '1.0'\nauthor: mahipal\nlicense: Apache-2.0\nd3fend_techniques:\n- Restore Access\n- Password Authentication\n- Biometric Authentication\n- Strong Password Policy\n- Restore User Account Access\nnist_csf:\n- ID.RA-01\n- GV.OV-02\n- DE.AE-07\nmitre_attack:\n- T1595\n- T1190\n- T1059\n- T1078\n- T1592\n---\n# Exploiting Active Directory with BloodHound\n\n\n> **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.\n\n## Overview\n\nBloodHound 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.\n\n\n## When to Use\n\n- When performing authorized security testing that involves exploiting active directory with bloodhound\n- When analyzing malware samples or attack artifacts in a controlled environment\n- When conducting red team exercises or penetration testing engagements\n- When building detection capabilities based on offensive technique understanding\n\n## Prerequisites\n\n- Familiarity with red teaming concepts and tools\n- Access to a test or lab environment for safe execution\n- Python 3.8+ with required dependencies installed\n- Appropriate authorization for any testing activities\n\n## Objectives\n\n- Collect Active Directory relationship data using SharpHound or BloodHound.py\n- Visualize attack paths from compromised accounts to Domain Admin\n- Identify misconfigured ACLs, group memberships, and delegation settings\n- Discover shortest attack paths to high-value targets\n- Map Kerberos delegation configurations for abuse\n- Document all identified privilege escalation chains\n\n## MITRE ATT&CK Mapping\n\n- **T1087.002** - Account Discovery: Domain Account\n- **T1069.002** - Permission Groups Discovery: Domain Groups\n- **T1482** - Domain Trust Discovery\n- **T1615** - Group Policy Discovery\n- **T1018** - Remote System Discovery\n- **T1033** - System Owner\u002FUser Discovery\n- **T1016** - System Network Configuration Discovery\n\n## Workflow\n\n### Phase 1: Data Collection with SharpHound\n1. Transfer SharpHound collector to compromised host\n2. Execute collection with appropriate method (All, DCOnly, Session, LoggedOn)\n3. Collect from all reachable domains if multi-domain environment\n4. Exfiltrate ZIP data files to analysis workstation\n5. Import data into BloodHound CE or Legacy\n\n### Phase 2: Attack Path Analysis\n1. Mark owned principals (compromised accounts)\n2. Query shortest path to Domain Admins\n3. Identify Kerberoastable accounts with admin privileges\n4. Find AS-REP Roastable accounts\n5. Analyze ACL-based attack paths (GenericAll, GenericWrite, WriteDACL, ForceChangePassword)\n6. Review GPO abuse opportunities\n\n### Phase 3: Exploitation Planning\n1. Prioritize attack paths by complexity and stealth\n2. Identify required tools for each step in the chain\n3. Plan OPSEC considerations for each technique\n4. Execute identified attack chain\n5. Document evidence at each step\n\n## Tools and Resources\n\n| Tool | Purpose | Platform |\n|------|---------|----------|\n| BloodHound CE | Graph visualization and analysis | Web-based |\n| SharpHound | AD data collection (.NET) | Windows |\n| BloodHound.py | AD data collection (Python) | Linux\u002FWindows |\n| Cypher queries | Custom graph queries | Neo4j\u002FBloodHound |\n| PlumHound | Automated BloodHound reporting | Python |\n| Max (BloodHound) | BloodHound automation | Python |\n\n## Key BloodHound Queries\n\n| Query | Purpose |\n|-------|---------|\n| Shortest Path to Domain Admins | Find fastest route to DA |\n| Find Kerberoastable Users with Path to DA | SPN accounts leading to DA |\n| Find AS-REP Roastable Users | Accounts without pre-auth |\n| Shortest Path from Owned Principals | Paths from compromised accounts |\n| Find Computers with Unsupported OS | Legacy systems for exploitation |\n| Find Users with DCSync Rights | Accounts that can replicate AD |\n| Find GPOs that Modify Local Group Membership | GPO-based privilege escalation |\n\n## Validation Criteria\n\n- [ ] SharpHound data collected from all domains\n- [ ] Attack paths identified from owned accounts to DA\n- [ ] ACL-based attack paths documented\n- [ ] Kerberoastable and AS-REP roastable accounts identified\n- [ ] Exploitation plan created with prioritized paths\n- [ ] Evidence screenshots captured for report\n","# Exploiting Active Directory with BloodHound\n\n\n> **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.\n\n## Overview\n\nBloodHound 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.\n\n\n## When to Use\n\n- When performing authorized security testing that involves exploiting active directory with bloodhound\n- When analyzing malware samples or attack artifacts in a controlled environment\n- When conducting red team exercises or penetration testing engagements\n- When building detection capabilities based on offensive technique understanding\n\n## Prerequisites\n\n- Familiarity with red teaming concepts and tools\n- Access to a test or lab environment for safe execution\n- Python 3.8+ with required dependencies installed\n- Appropriate authorization for any testing activities\n\n## Objectives\n\n- Collect Active Directory relationship data using SharpHound or BloodHound.py\n- Visualize attack paths from compromised accounts to Domain Admin\n- Identify misconfigured ACLs, group memberships, and delegation settings\n- Discover shortest attack paths to high-value targets\n- Map Kerberos delegation configurations for abuse\n- Document all identified privilege escalation chains\n\n## MITRE ATT&CK Mapping\n\n- **T1087.002** - Account Discovery: Domain Account\n- **T1069.002** - Permission Groups Discovery: Domain Groups\n- **T1482** - Domain Trust Discovery\n- **T1615** - Group Policy Discovery\n- **T1018** - Remote System Discovery\n- **T1033** - System Owner\u002FUser Discovery\n- **T1016** - System Network Configuration Discovery\n\n## Workflow\n\n### Phase 1: Data Collection with SharpHound\n1. Transfer SharpHound collector to compromised host\n2. Execute collection with appropriate method (All, DCOnly, Session, LoggedOn)\n3. Collect from all reachable domains if multi-domain environment\n4. Exfiltrate ZIP data files to analysis workstation\n5. Import data into BloodHound CE or Legacy\n\n### Phase 2: Attack Path Analysis\n1. Mark owned principals (compromised accounts)\n2. Query shortest path to Domain Admins\n3. Identify Kerberoastable accounts with admin privileges\n4. Find AS-REP Roastable accounts\n5. Analyze ACL-based attack paths (GenericAll, GenericWrite, WriteDACL, ForceChangePassword)\n6. Review GPO abuse opportunities\n\n### Phase 3: Exploitation Planning\n1. Prioritize attack paths by complexity and stealth\n2. Identify required tools for each step in the chain\n3. Plan OPSEC considerations for each technique\n4. Execute identified attack chain\n5. Document evidence at each step\n\n## Tools and Resources\n\n| Tool | Purpose | Platform |\n|------|---------|----------|\n| BloodHound CE | Graph visualization and analysis | Web-based |\n| SharpHound | AD data collection (.NET) | Windows |\n| BloodHound.py | AD data collection (Python) | Linux\u002FWindows |\n| Cypher queries | Custom graph queries | Neo4j\u002FBloodHound |\n| PlumHound | Automated BloodHound reporting | Python |\n| Max (BloodHound) | BloodHound automation | Python |\n\n## Key BloodHound Queries\n\n| Query | Purpose |\n|-------|---------|\n| Shortest Path to Domain Admins | Find fastest route to DA |\n| Find Kerberoastable Users with Path to DA | SPN accounts leading to DA |\n| Find AS-REP Roastable Users | Accounts without pre-auth |\n| Shortest Path from Owned Principals | Paths from compromised accounts |\n| Find Computers with Unsupported OS | Legacy systems for exploitation |\n| Find Users with DCSync Rights | Accounts that can replicate AD |\n| Find GPOs that Modify Local Group Membership | GPO-based privilege escalation |\n\n## Validation Criteria\n\n- [ ] SharpHound data collected from all domains\n- [ ] Attack paths identified from owned accounts to DA\n- [ ] ACL-based attack paths documented\n- [ ] Kerberoastable and AS-REP roastable accounts identified\n- [ ] Exploitation plan created with prioritized paths\n- [ ] Evidence screenshots captured for report\n",{"name":5,"tags":25,"author":33,"domain":34,"license":15,"version":35,"nist_csf":36,"subdomain":40,"description":7,"mitre_attack":41,"d3fend_techniques":47},[26,27,28,29,30,31,32],"red-team","adversary-simulation","mitre-attack","exploitation","post-exploitation","active-directory","bloodhound","mahipal","cybersecurity","1.0",[37,38,39],"ID.RA-01","GV.OV-02","DE.AE-07","red-teaming",[42,43,44,45,46],"T1595","T1190","T1059","T1078","T1592",[48,49,50,51,52],"Restore Access","Password Authentication","Biometric Authentication","Strong Password Policy","Restore User Account Access","main","7540bbccf0c1ded6156a467b02c95b61ad62413f",".agents\u002Fskills\u002Fexploiting-active-directory-with-bloodhound","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena","Currently exploring the intersection of tech","2026-09-11 03:02:31",{"source":8,"skillName":5,"commands":61,"prompt":71,"zipAvailable":72},[62,65,68],{"tool":63,"command":64},"npx","npx skills add NeelakshSaxena\u002FVayu --skill exploiting-active-directory-with-bloodhound",{"tool":66,"command":67},"bunx","bunx skills add NeelakshSaxena\u002FVayu --skill exploiting-active-directory-with-bloodhound",{"tool":69,"command":70},"pnpm","pnpm dlx skills add NeelakshSaxena\u002FVayu --skill exploiting-active-directory-with-bloodhound","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fexploiting-active-directory-with-bloodhound\u002FSKILL.md",true,[74,80,84,90,94,98,104],{"path":75,"resourceType":76,"resourceTypeDesc":77,"sizeBytes":78,"sourceHtmlUrl":79},"assets\u002Ftemplate.md","ASSET","资产文件",1821,"https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fexploiting-active-directory-with-bloodhound\u002Fassets\u002Ftemplate.md",{"path":81,"resourceType":81,"resourceTypeDesc":82,"sizeBytes":83,"sourceHtmlUrl":16},"LICENSE","许可证",11255,{"path":85,"resourceType":86,"resourceTypeDesc":87,"sizeBytes":88,"sourceHtmlUrl":89},"references\u002Fapi-reference.md","REFERENCE","参考文档",2331,"https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fexploiting-active-directory-with-bloodhound\u002Freferences\u002Fapi-reference.md",{"path":91,"resourceType":86,"resourceTypeDesc":87,"sizeBytes":92,"sourceHtmlUrl":93},"references\u002Fstandards.md",3526,"https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fexploiting-active-directory-with-bloodhound\u002Freferences\u002Fstandards.md",{"path":95,"resourceType":86,"resourceTypeDesc":87,"sizeBytes":96,"sourceHtmlUrl":97},"references\u002Fworkflows.md",6274,"https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fexploiting-active-directory-with-bloodhound\u002Freferences\u002Fworkflows.md",{"path":99,"resourceType":100,"resourceTypeDesc":101,"sizeBytes":102,"sourceHtmlUrl":103},"scripts\u002Fagent.py","SCRIPT","脚本",5751,"https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fexploiting-active-directory-with-bloodhound\u002Fscripts\u002Fagent.py",{"path":105,"resourceType":100,"resourceTypeDesc":101,"sizeBytes":106,"sourceHtmlUrl":107},"scripts\u002Fprocess.py",22080,"https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fexploiting-active-directory-with-bloodhound\u002Fscripts\u002Fprocess.py",[109,116,123,130,137,144],{"skillNo":110,"name":111,"nameZh":6,"description":112,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":113,"categories":114,"keywords":115,"publishedAt":20},"01M7ACCCVNCFKMA9X6D15X6G98","runpodctl","Runpod CLI for managing GPU\u002FCPU workloads from the terminal — pods, serverless endpoints, templates, network volumes, Hub deploys, models, SSH, and file transfer (send\u002Freceive). Use for terminal\u002FCI\u002Fscripting, Hub browse\u002Fdeploy, SSH setup, `doctor`, or when the Runpod MCP tools are not connected. For structured tool calls in an MCP-enabled session, prefer runpod-mcp.","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Frunpodctl\u002FSKILL.md",[],[],{"skillNo":117,"name":118,"nameZh":6,"description":119,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":120,"categories":121,"keywords":122,"publishedAt":20},"01M7ACC63SRHEA5KMCHSMZK2TC","runpod","Start here for any Runpod task — running GPU\u002FCPU 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.","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Frunpod\u002FSKILL.md",[],[],{"skillNo":124,"name":125,"nameZh":6,"description":126,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":127,"categories":128,"keywords":129,"publishedAt":20},"01M7ACC0Q1C89N9BZBV91CTQTF","runpod-usage","How Runpod works and how to work it — pods vs serverless, GPU\u002FVRAM 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\u002Fapt). 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.","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Frunpod-usage\u002FSKILL.md",[],[],{"skillNo":131,"name":132,"nameZh":6,"description":133,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":134,"categories":135,"keywords":136,"publishedAt":20},"01M7ACBRPE345GF5GM5B8P8RRC","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 \u003CX> 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.","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Frunpod-templates\u002FSKILL.md",[],[],{"skillNo":138,"name":139,"nameZh":6,"description":140,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":141,"categories":142,"keywords":143,"publishedAt":20},"01M7ACBJATHKVX1TWES2F44GY8","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.","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Frunpod-migrate\u002FSKILL.md",[],[],{"skillNo":145,"name":146,"nameZh":6,"description":147,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":148,"categories":149,"keywords":150,"publishedAt":20},"01M7ACBC7GHVH6T9YEAPCG2AP8","runpod-mcp","Manage Runpod infrastructure — pods, serverless endpoints, jobs, templates, network volumes, container-registry auth, GPU\u002FCPU 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.","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Frunpod-mcp\u002FSKILL.md",[],[]]