Security Ops
Collapse noisy probe traffic into families and rank suspicious payload clusters before writing full parser logic.
precursor.hashdb.io
Precursor tags, clusters, and prioritizes packet, log, and firmware payloads with one JSON-first CLI. It is built for early-stage triage where you need signal now, not after parser engineering.
Precursor is the bridge between "we have weird bytes" and "we can confidently scope response or build deeper detection."
Collapse noisy probe traffic into families and rank suspicious payload clusters before writing full parser logic.
Tag binary fragments and filesystem magic quickly so analysts can prioritize which artifacts deserve deeper reverse engineering.
Start with Sigma/PCRE labeling, then use similarity + stats to refine into stable, explainable signal.
Click a scenario to inspect command, real output, and run stats captured from public sample corpora.
This visual shows how adding targeted tags changes measurable signal across iterations, not just intuition.
Local Codex CLI consumed Precursor stats + sample NDJSON, proposed a new pattern, then we validated the command on the same corpus.
Risk:
--statsTrack payload volume and size distribution so performance regressions or capture shifts are obvious.
See which tags dominate and whether new patterns add precision or just noise.
Validate similarity mode, distance behavior, and runtime context when sharing findings or benchmarking.
cargo install precursor
cat samples/scenarios/pre-protocol-packet-triage/payloads.b64 \
| precursor -p samples/scenarios/pre-protocol-packet-triage/patterns.pcre \
-m base64 -t -d --similarity-mode lzjd -P --protocol-hints --stats
Background inspiration and historical context: blog post 1 and blog post 2.