Malware must run
Why this blog exists...
Malware must run. Controlled, observed, understood. That’s the methodology.
You can read about Process Injection, Anti-Analysis, Shellcode, etc. But, to understand that, and become a better analyst, sometimes you end up running the thing yourself. Watching it land. Seeing what the telemetry shows, and what it doesn’t.
That’s what this site is about. Here I’ll post my analysis, writeups, as I’m learning along the way.
I started my career as a Pentester, and now work in CTI. I usually say that knowing how to attack actually makes you a better defender. I love to analyze Malware, work in Phishing Detection and Analysis, and automate workflows and pipelines to try to make my life easier. I hold certifications such as OSCP, OSCE, GREM, and others.
I have some ideas on what I want to build right now, as I have some courses lined up already, and I thought about creating this website to document my process and produce some content.
Older content from my previous blog (bufferoverflowed.wordpress.com) such as Practical Malware Analysis writeups, and SLAE32|64 assignments, will also live here as an archive. Those represent where I was. What I’ll be writing going forward represents where I’m going.
I’m not trying to be a tutorial site. I’m documenting my own learning because the act of writing forces precision, and because someone else working through the same problems might find it useful.
Malware must run.