Articles

Reverse engineering, explained through real samples

Practical guides for analysts working on actual binaries. What each stage of static analysis proves, what individual Windows APIs imply, and where everyone tends to misread them.

Start here

Reverse engineering a malware sample: a practical introduction

The static analysis pipeline in the order analysts actually use it: file identification, import table, strings, control flow, decompilation. Plus how to tell when static analysis has stopped paying and it is time to let the sample run.

Pillar ~9 min
Windows API behaviour

What CreateRemoteThread tells you about a binary

The classic process injection primitive: the four-call sequence that makes it conclusive, the legitimate software that injects too (your antivirus, for one), and how to confirm intent from cross-references instead of from the import alone.

API ~5 min

Apply this to your own sample

FastBin runs the static pipeline for you: format identification, imports, strings, function recovery and Ghidra decompilation. There is an isolated sandbox for when you need to watch it actually run.

Analyse a sample