Reverse engineering

Closed binary, legacy without source, behavior to understand — we dive in.

You inherited a binary without sources, need to understand a proprietary protocol, analyze a malware or recover the logic of an app abandoned by its vendor? That's what reverse engineering is for: disassemble, understand, document. I work on Windows and Linux, primary focus on .NET binaries (IL/CIL) and native x86/x64/ARM. Output: usable technical doc + recommendations.

Tarif

On quote

Response within 48 business hours.

Included

✓ Static analysis (Ghidra, IDA, dnSpy, JEB)
✓ Dynamic analysis when needed (debugger, network capture)
✓ Documentation of behavior / protocol / data structures
✓ If relevant: readable POC code reproducing the logic
✓ Final report + handover, NDA always

FAQ

Frequently asked questions

No. I always ask for legal context before starting: project recovery you own rights to, legitimate interoperability (allowed under French/EU law), security audit on your own product. No cracking of commercial protections for license bypass.

Specialty: .NET (managed, IL/CIL) where I'm very efficient. Also native Windows (PE x86/x64) and Linux (ELF), Android (APK/native), ARM Cortex-M firmware. For iOS/macOS, we look — more case-dependent.

Really depends. Understanding a simple file format: 1-2 days. Reversing a medium .NET app: 1-3 weeks. Quote after a short exploratory phase (often half a day offered for scoping).

Yes, for post-incident forensic analysis (you were hit, you want to know what happened). Not for developing offensive tools.

Quote

Reverse engineering

Name

Company

Phone (optional)

Budget

Describe your project

Response within 48 business hours.