darkrecon

Dark-web / OSINT reconnaissance for threat intelligence

v1.2.1
Linux

Quick Start

Install via jcli (recommended)

jcli install darkrecon

Run a lookup

darkrecon domain example.com                       # crt.sh subdomain enum
darkrecon hash 5baa61e4c9b93f3f0682250b6cf8331b7ee68fd8   # HIBP k-anonymity
darkrecon config --list                            # show configured API keys (masked)
darkrecon config --set virustotal_key <KEY>        # store a key (chmod 600)

What it does

darkrecon is a multi-source OSINT lookup CLI. Subcommands one-shot a specific kind of input — a domain, an email, a SHA-1 — against the right upstream source. Two sources need no API key (crt.sh and HIBP); the rest require an operator-stored key. Designed for the threat-intel analyst use case where you have one IOC and want every external context in one command.

Subcommands

CommandStatusWhat it does
domain <DOMAIN>workingcrt.sh subdomain enumeration (no API key needed)
hash <SHA1>workingHIBP pwnedpasswords k-anonymity check (no API key needed)
email <ADDR>stubHIBP v3 breach API — needs hibp_breach_key
bulk -f <PATH>stubAuto-detect-per-line + interleaved-throttle multi-source lookup
config --set KEY VALUEworkingStore an API key in keys.toml (chmod 600)
config --listworkingShow configured keys, first 4 chars only

Sources catalogue

SourceStatusNotes
crt.shworkingNo key. Slow (occasional 502/503). Used by domain
HIBP pwnedpasswordsworkingNo key. k-anonymity. Used by hash
HIBP v3 breach APIstubNeeds hibp_breach_key
VirusTotalstubNeeds vt_key. File hash, URL, IP, domain reputation
ShodanstubNeeds shodan_key. Host services + exposed-port intelligence
IntelXstubNeeds intelx_key. Leak-site search
URLScanstubNeeds urlscan_key. Public scan results for a given URL
PhishTankstubNeeds phishtank_key. Community-reported phishing URLs

Privacy: the working sources are designed to leak the minimum about your queries — HIBP's k-anonymity sends only the SHA-1 prefix, crt.sh queries leak the queried domain (unavoidable). Future sources (VirusTotal, Shodan, IntelX) send the full IOC in the clear to the upstream — operator should review each source's privacy policy before automating queries about client IOCs.