A DECOMPILER IS ONLY STAGE ONE

The eight-stage EX5 evidence pipeline

Most tools stop at parsing a file or emitting raw disassembly. Our backend continues through eight coordinated stages, each forced to agree with the last — turning an opaque binary into a confidence-scored technical case.

FingerprintMapObserveLiftExploreReasonChallengeScore
“Most tools give you a view. This pipeline is built to build a technical case.”
01
STAGE 01 · FINGERPRINT

Characterize the artifact

Identify container properties, architecture signals, integrity conditions, compiler and build indicators, and version-sensitive constraints — the profile everything downstream is calibrated against.

Reads
.ex5 bytes
Writes
build profile
Engines
Custom .NET parsers
02
STAGE 02 · MAP

Recover the structure

Recover accessible code and data regions, candidate functions, references, call relationships, control flow, constants, strings, and platform interactions into a navigable structural map.

Reads
fingerprint + bytes
Writes
functions · CFG · xrefs
Engines
IDA · Ghidra · radare2
03
STAGE 03 · OBSERVE

Confirm behavior at runtime

Where the target and authorization permit, scripted instrumentation collects reproducible execution evidence — transitions, register and memory state, module and call-path activity — under defined, logged conditions.

Reads
structural map
Writes
runtime traces
Engines
x64dbg · WinDbg · Frida · DynamoRIO · Pin
04
STAGE 04 · LIFT

Normalize into IR

Lift low-level instructions into an architecture-aware intermediate representation modeling blocks, calls, state, types, and side effects — the common language every later stage reasons over.

Reads
static + runtime evidence
Writes
IR + evidence graph
Engines
Proprietary IR
05
STAGE 05 · EXPLORE

Prune the candidate space

Evaluate competing interpretations under structural, data-flow, type, calling-convention, platform, and runtime constraints — eliminating everything the evidence forbids and ranking what survives.

Reads
IR + constraints
Writes
ranked candidates
Engines
Constraint solver
06
STAGE 06 · REASON

Apply specialist AI

Authorized high-capability models classify routines, infer types and roles, correlate distant evidence, and flag ambiguity — proposing hypotheses, never declaring verdicts.

Reads
ranked candidates
Writes
semantic hypotheses
Engines
OpenAI · Anthropic APIs
07
STAGE 07 · CHALLENGE

Force the evidence to agree

Compare independent passes, expose contradictions, reject incompatible hypotheses, and return ambiguous regions for deeper analysis before anything is allowed to progress.

Reads
hypotheses + evidence
Writes
reconciled findings
Engines
Differential validators
08
STAGE 08 · SCORE

Deliver with confidence

Label each finding by evidentiary strength — verified, high, probable, tentative, or unresolved — so a strong result in one region never disguises uncertainty in another.

Reads
reconciled findings
Writes
confidence-scored .mq5
Engines
Scoring + report gate
WHY EIGHT STAGES

No single tool decides the answer

One disassembler gives a view. One debugger gives a trace. One model gives an opinion. The pipeline correlates them, rejects candidates the binary forbids, records provenance, and only promotes a finding once independent evidence agrees.

Evidence from every stage is correlated in one shared representation.
Candidates that violate binary constraints are rejected, not smoothed over.
Provenance and blockers are recorded at each stage boundary.
Confidence is assigned per finding — conflicts lower it instead of hiding.

Run all eight stages on your own EX5

Review the published license terms and preview the planned checkout experience for the local Windows workflow. The current demo does not accept payment or issue software.

Review licensingBack to overview
Eight-Stage Evidence Pipeline | Snake EX5 Decompiler