I build low-level systems, break things in CTF competitions, and write code in Rust because life's too short for segfaults you didn't choose.
I'm Sebastian Toro, and I operate at the intersection of systems programming and security research. The kind of developer who finds joy in understanding how things work three layers deeper than anyone asked.
I got into programming because I wanted to understand computers — not just use them. That curiosity led me down the rabbit hole of low-level programming, reverse engineering, and CTF competitions.
When I'm not hunting vulnerabilities or writing Rust, I'm exploring Elixir and Gleam — because functional programming deserves more love.
Security isn't about paranoia — it's about understanding systems deeply enough to know where they break. The best defense comes from knowing the attack.
Each area feeds into the others, making me better at all of them.
Building robust, performant software at the lowest levels. Memory management, concurrency, and code that doesn't just work — it works fast.
Reverse engineering binaries, finding vulnerabilities, and understanding how systems fail. Every bug is a lesson.
Blog posts and CTF writeups to solidify understanding. If you can't explain it clearly, you don't really know it.
The best way to understand a system is to try to break it. The second best way is to build one yourself.
— How I approach every challenge
Every language shapes how you think about problems. I'm drawn to languages that give you control, expressiveness, or both.
Memory safety without garbage collection. Fearless concurrency. A type system that catches bugs before they become vulnerabilities. It's the language I wish I'd had when I was writing C.
CTF competitions — where security theory meets practice. Find the flag hidden in the binary, the web app, or the cipher.
Hours of staring at assembly, tweaking ROP chains, adjusting offsets — then the flag appears. That dopamine hit is unmatched. I focus on binary exploitation and reverse engineering.
After every competition, I write detailed breakdowns. Not just the solution — the thought process, the dead ends, the "aha" moments. Writing forces clarity.
Curiosity → rabbit holes → low-level love → competitive hacking → Rust.
From security tools to systems utilities — software built with intent.
Custom tools for binary analysis and exploitation. Built in Rust for speed and safety.
Pwntools wrappers, solver templates, and exploit primitives that save hours in competition.
Deep-dive analysis of real-world software. Identifying attack surfaces and documenting findings.
Low-level utilities: parsers, allocators, OS-level tools — the building blocks everything depends on.
I write because it forces me to understand things deeply.
Security questions, project ideas, or just talking about why Rust is the best — I'm always happy to hear from interesting people.