I break things on purpose so they hold up in production. My focus is finding exploitable weaknesses in real-world codebases, proving impact with working reproductions, and turning findings into durable fixes that maintainers can trust.
Proud member of Team CODEOPS47.
- π― Offensive Security Research
- π Exploit Development
- π§ͺ Fuzzing & Coverage Analysis
- π Protocol & Network Auditing
- 𧡠Concurrency & State-Machine Bugs
- π₯ Input & Deserialization Attacks
- π¬ Crash Triage & Root Cause
- π€ Upstream Collaboration
Use-After-Free
Heap & Stack Overflows
Deserialization Flaws
TOCTOU & Race Conditions
Logic & Authorization Bugs
Type Confusion
Sandbox Escapes
Supply-Chain Integrity
Defense-in-Depth
Vulnerability Research
Exploit Engineering
Fuzz Harness Design
Reverse Engineering
Patch Review
Threat Modeling
Responsible Disclosure
Map the attack surface.
Question every trust boundary.
Build a reliable repro.
Prove real impact.
Disclose responsibly.
Ship the hardened fix.
Leave a test behind.
- Exploit primitive development
- Memory-corruption discovery
- Fuzzing campaign design
- Protocol state-machine analysis
- Deserialization audits
- Responsible disclosure reports
- Security hardening patches
- Fuzz harness contributions
- Bug fixes with regression tests
- Reliability improvements
- Maintainer-friendly PRs
β Thanks for stopping by.
