https://github.com/mordavid/NetworkHound
NetworkHound connects to Active Directory Domain Controllers, discovers computer objects, resolves hostnames to IP addresses using multiple DNS methods, performs comprehensive network scanning (port scanning, HTTP/HTTPS validation), and discovers shadow-IT devices.
It then builds a detailed network topology graph in OpenGraph JSON format compatible with BloodHound.
Authentication supports password, NTLM and Kerberos, so it fits into an engagement wherever you are on the credential ladder.
Example usage (commands from the README):
# Basic scan with AD credentials
python NetworkHound.py --dc 192.168.0.11 -d company.local -u admin -p password
# Full analysis: port scan, HTTP/S/SSL and SMB validation, shadow-IT sweep
python NetworkHound.py --dc 192.168.0.11 -d company.local -u admin -p password \
--shadow-it --port-scan --valid-http --ssl --valid-smb --scan-threads 50 -Pn
# NTLM hash authentication (LM:NT or just NT)
python NetworkHound.py --dc 192.168.0.11 -d company.local -u admin \
--hashes aad3b435b51404eeaad3b435b51404ee:5fbc3d5fec8206a30f4b6c473d68ae76
# DNS over TCP — needed when egress goes through a SOCKS proxy
proxychains python NetworkHound.py --dc dc.company.local -d company.local \
-u admin -p password --dns-tcp --port-scanThe proxychains case is a real-trip detail the README calls out: UDP DNS breaks through SOCKS proxies, so --dns-tcp is not optional there.