Credentials
Passwords, hashes, session cookies — across plaintext dumps, SQL exports, and old config files.
Six categories, one pass. BLINK pulls high-signal items out of raw dumps using a curated signature library — not a model that hallucinates secrets that aren't there.
Passwords, hashes, session cookies — across plaintext dumps, SQL exports, and old config files.
Live keys for AWS, GCP, Stripe, Slack, GitHub, OpenAI, Twilio and 240 other providers.
Names, emails, DOB, government IDs, addresses, payment data — flagged with their jurisdiction.
Private keys (RSA, EC, Ed25519), wallet seeds, recovery phrases and certificate chains.
Hostnames, S3 buckets, VPN endpoints, Kubernetes namespaces — anything that maps the attack surface.
Emails, chat logs and ticket threads — clustered by participant, redacted, full-text searchable.
No buckets to configure, no models to wait on. The whole pipeline runs locally and finishes before your coffee.
Any envelope BLINK knows how to crack — .zip, .tar.gz, .7z, .sql, .pcap, even nested 12 levels deep. SHA-256 is computed inline so the fingerprint is ready before extraction finishes.
2,184 hand-tuned signatures sweep every byte. OCR for scanned PDFs and screenshots. Entropy scoring catches the secrets we don't have a pattern for yet.
Findings are sorted by blast radius, deduped against the noise floor, and cross-linked to the identities they belong to. Export to SARIF, JSON, CSV or a one-page exec PDF.
One pane. Severity-sorted. Every finding is a path, a line number, and a redacted preview you can copy with one keystroke. Below is the report BLINK produced from a fabricated "WyndCorp" breach dump — same shape as the real thing.
BLINK is used in incident response, M&A diligence, journalism, threat-intel, and litigation discovery. Numbers below are aggregated from opt-in telemetry across v2 and v3.