About Me

I’m Davi Santana, a cybersecurity enthusiast focused on reverse engineering, malware analysis, and low-level software research.

This blog is where I document my studies, experiments, and technical research around understanding how software works beneath the surface. My main interests include malware analysis, reverse engineering, debugging, Windows internals, binary analysis, and offensive security.

What I Do

I spend most of my time analyzing binaries and breaking down their behavior through a combination of static and dynamic analysis. My work often involves tools such as IDA Pro, x64dbg, OllyDbg, EDB, HxD, and other tools commonly used in binary analysis and debugging.

I’m particularly interested in understanding the complete execution flow of a program — from its entry point and low-level instructions to API calls, memory manipulation, persistence mechanisms, obfuscation, and network behavior.

What You’ll Find Here

This blog is mainly a technical notebook and knowledge base. I write about:

  • Malware analysis and reverse engineering
  • Static and dynamic binary analysis
  • Windows internals and low-level programming
  • Debugging and assembly
  • CTFs, labs, and practical security exercises
  • Obfuscation and anti-analysis techniques
  • Vulnerability research and offensive security
  • Technical notes from certifications and courses

The goal isn’t just to show the final answer, but to document how the analysis was performed, the reasoning behind each step, and what can be learned from it.

Why Reverse Engineering?

Reverse engineering gives me the opportunity to understand software from the inside out.

Instead of treating a binary as a black box, I like to investigate its instructions, memory, APIs, control flow, and interactions with the operating system to understand what it actually does.

That mindset is especially valuable in malware analysis, where the source code is usually unavailable and the analyst has to reconstruct the behavior from evidence.

Keep Learning

I’m constantly learning, experimenting, and documenting the process.

This blog represents that journey — one binary, one function, and one debugging session at a time.

Understand the code. Understand the behavior. Understand the binary.