Hey Everyone,
My journey in cybersecurity started with application security, and over time, shifted deeper into the world of product & content security. But if I’m being honest, the thing that’s always pulled me in — the thing I keep coming back to — is reverse engineering. It’s like a puzzle I can’t resist.
It’s been over four years since I last actively blogged — right around the start of the COVID pandemic. Since then, I’ve dedicated myself to growing both professionally and personally. During this period, I’ve been quietly learning, building tools, and exploring all kinds of interesting stuff, like:
- Binary analysis
- Emulator development
- Compiler internals, especially data flow analysis technique focused on static analysis
- OS Internals
- Different obfuscation methods and how to break through them
- Dynamic Binary Instrumentation, Symbolic Execution, and other techniques
- Open source project fuzzing — finding bugs by poking at source code
- Machine learning basics, mostly for things like device fingerprinting, de-obfuscation … etc
- and more
But honestly? I never found the time to share much of this with anyone. That changes now.
Maybe you’ve seen bits of my work scattered across GitHub or Fools Of Security, but this time, I wanted a place that really reflects the direction I’m heading in.
So here we go announcing: IR2RE — Interrupt Return to Reverse Engineering.
If you’re wondering about the name, it’s a little nod to the IRET (Interrupt Return) instruction in x86 CPUs. That’s the moment when the processor returns from handling an interrupt and picks up where it left off. Kind of like me, coming back to what I love: reverse engineering.
Here’s what I’ll be sharing:
- Product Security: Real world challenges and practical insights
- Reverse Engineering: Breaking down binaries, tackling obfuscation at scale, and more
- Tools in Python & Rust: Building better automation and analysis tools
- Vulnerability Research: From static analysis and fuzzing to exploit development
My first proper post is coming very soon. Stay tuned!
— ir2re