RustHound-CE is a cross-platform and cross-compiled BloodHound collector tool written in Rust, making it compatible with Linux, Windows, and macOS. It therefore generates all the JSON files that can be analyzed by BloodHound Community Edition. This version is only compatible with BloodHound Community Edition. The version compatible with BloodHound Legacy can be found on NeverHack’s github.

RustHound was created during my years as a pentester at Armature Technologies, renamed later Opencyber then NeverHack. I would like to thanks NeverHack for giving me time to research and develop the original RustHound project, which is still available on their github. We’ve decided to continue working together to contribute to both versions. This one will remain compatible with the community edition, and the NeverHack version with the Legacy version of BloodHound.

• HELP.md - How to compile it? How to install it? How to use it?
• CHANGELOG.md - A record of all significant version changes
• ROADMAP.md - List of planned evolutions
• LINKS.md - Useful resources

Quick usage

Compilation

This project can be compiled directly from make command like:

# Compile it for your current system
make release
# Compile it for Windows
make windows

Or using docker like below:

docker build --rm -t rusthound-ce .

# Then
docker run --rm -v $PWD:/usr/src/rusthound-ce rusthound-ce help
docker run --rm -v $PWD:/usr/src/rusthound-ce rusthound-ce release
docker run --rm -v $PWD:/usr/src/rusthound-ce rusthound-ce windows
docker run --rm -v $PWD:/usr/src/rusthound-ce rusthound-ce linux

Installation

Make sure the required dependencies are installed.

# Install and/or update RustHound-CE from cargo command
cargo install rusthound-ce

Usage

Here’s an example of a command to collect domain objects and obtain the zip archive containing the json files to be imported into BloodHound CE:

rusthound-ce -d DOMAIN.LOCAL -u [email protected] -z

More information and examples with how to compile RustHound-CE or how to use RustHound-CE can be found directly on the help page.

Special thanks to