Executable Binaries
Managed Code
Documents
Email & Messaging
Disk Images & Installers
Scripts
Forensic Artifacts
Forensic file types are a recent addition. They enable investigation of Windows event logs, network traffic, and execution evidence.
Firmware
How Detection Works
DECODA uses a multi-stage detection pipeline:1
Magic Bytes
The first 4-16 bytes of the file are checked against known signatures (MZ, ELF, PDF, OLE, etc.).
2
Structural Analysis
For ambiguous types (ZIP-based files, OLE documents), DECODA inspects internal structure to distinguish JAR from OOXML, MSG from OLE, or MSI from Office documents.
3
Deep Inspection
PE files are checked for .NET metadata (BSJB signature), UEFI subsystems, and packer signatures. Unknown blobs are tested with capstone for shellcode instruction density.
4
Tool Routing
The detected type determines which tools are recommended, discouraged, and prioritised. This guidance is passed to the AI agent, which makes final tool selection decisions.
- 90-100 - High confidence (multiple strong indicators)
- 70-89 - Good confidence (clear magic bytes, valid structure)
- 50-69 - Medium confidence (partial matches, some ambiguity)
- 0-49 - Low confidence (heuristic guesses)