#️⃣ File Hash
Cryptographic fingerprint of a file, used for malware identification.
Cyber
🔧 Native workbench
🔎 Live indicators (IoC view)
🔗 Analyst pivots
🔌 Sources that yield File Hash (7)
| Source | Category | Auth | Format | |
|---|---|---|---|---|
| abuse.ch SSLBL JA3 Fingerprints Malicious TLS client JA3 fingerprint blocklist. | CERTINT | NONE | csv | home↗ api↗ |
| APTnotes Public archive of APT research reports. | APT | NONE | json | home↗ api↗ |
| MITRE ATT&CK Groups (STIX) Adversary groups, software and techniques. | APT | NONE | json | home↗ api↗ |
| MITRE ATT&CK Software/Actors Adversary tooling & group knowledge base. | ACTORINT | NONE | json | home↗ api↗ |
| ORKL Threat Report Library Full-text CTI report library API. | APT | NONE | json | home↗ api↗ |
| AlienVault OTX Pulses Community threat-intel pulses (free key). | Threat Analysis | KEY | json | home↗ api↗ |
| Malpedia Curated malware family encyclopedia. | MALINT | KEY | json | home↗ api↗ |
🧭 Disciplines
🎯 Mission Domains
🔍 Lookup
🔄 Live Datasets & APIs (5 key-free · ingestible)
📜 Playbook — File Hash exploitation
- Direction — frame the requirement for File Hash: what decision does this support, by when?
- Collection — pull the 7 mapped sources (5 free) and the native workbench (open); capture provenance and observe OPSEC.
- Processing — normalize, de-duplicate and enrich the collected data.
- Analysis — correlate against local holdings; apply ACH; assign confidence.
- Dissemination — open a case, draft a report, share via STIX/MISP.
- Feedback — set an alert rule / watchlist to monitor for change.
⚡ AI Skills & Automation
Automate unattended via the cron pipeline (collect → ingest → resolve → enrich → score → alert).
🧩 Advanced Capabilities
✨ Enrichment pathways
🎫 File Hash
A file hash is a fixed-length cryptographic digest (MD5, SHA-1, SHA-256) or fuzzy/import hash (ssdeep, imphash, TLSH) that uniquely fingerprints a file's contents. It matters because it is the atomic IOC for identifying known-bad binaries, deduplicating samples, and pivoting to malware families and campaigns.
Format: 32/40/64 hex chars (MD5/SHA-1/SHA-256); imphash 32 hex; ssdeep chunked base64 (blocksize:hash:hash); TLSH 70 hex; authentihash for PE signing.
📡 How it is collected
- EDR/AV telemetry and quarantine logs
- Sandbox detonation output (Cuckoo/CAPE)
- Email gateway & proxy attachment logging
- Threat-intel feeds and ISAC sharing
- Static computation over collected file corpus
- Memory dumps and forensic disk images
📚 Enrichment & validation sources
🔗 Pivot to
🧩 Analysis & hunting techniques
- Multi-AV consensus & detection-name normalization
- Fuzzy-hash (ssdeep/TLSH) similarity clustering
- Imphash pivoting on shared import tables
- YARA retro-hunt across sample corpus
- Known-good filtering via NSRL allowlisting
- Code-similarity / genetic analysis (Intezer)
- Signer-cert reuse tracking
- First-seen / prevalence timelining
🔧 Tools
- YARA
- ssdeep / TLSH
- PE-bear / pefile
- CAPA (Mandiant)
- Detect It Easy (DIE)
- vt-cli
- capev2 sandbox
⚡ Workbench actions
- Look up multi-source reputation
- Detonate in sandbox
- Generate YARA rule
- Cluster by fuzzy hash
- Pivot to C2 infrastructure
- Check NSRL known-good
- Extract imphash & signer
- Retro-hunt corpus
📊 Dashboard KPIs
AV detection ratioFirst-seen date / ageSample prevalence countFuzzy-hash cluster sizeFamily attribution confidence
Workstation · Copilot · AI Skills · Automation · Playbooks · Lookups · Docs · Reports
🤖 AI Copilot
⚡ AI Skills
🔍 Lookup & Enrich
📚 Docs & Reports
💡 Recommendations
- Explore related tools below
- Automate recurring work via cron