Skip to content

fix: correctly load real SharpHound collection files + add full --debug flag#12

Merged
DotNetRussell merged 1 commit intomainfrom
features/bunch-of-new-features
Feb 18, 2026
Merged

fix: correctly load real SharpHound collection files + add full --debug flag#12
DotNetRussell merged 1 commit intomainfrom
features/bunch-of-new-features

Conversation

@DotNetRussell
Copy link
Copy Markdown
Owner

Summary
Fixed the loader so BloodBash now properly reads real SharpHound JSON collection files (the ones with top-level keys like "users", "computers", "groups", "domains", etc.).
Also added a new --debug flag that provides detailed verbose output during parsing, graph building, and analysis to make troubleshooting much easier.
Changes

Updated load_json_dir() to detect and use the correct collection key from SharpHound files
Added comprehensive --debug logging throughout loading, graph building, and analysis functions
Bumped version to 1.2.3
Minor cleanup and improved debug messages

Testing
Bash./BloodBash /path/to/SharpHound_Data/ --all --debug
The tool should now show:

"Using collection key 'users' (list of X items)"
Full object counts per file
Graph build stats
No more "Loaded 0 objects" error

Related
Closes the issue where BloodBash was unable to parse standard SharpHound output.

@DotNetRussell DotNetRussell merged commit 7eea215 into main Feb 18, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant