“I don’t do small talk. But I do deep technical conversation.”
If you’re here, you probably have something worth saying. I’m reachable through the channels below — pick whichever fits your context.
When to Reach Out
I’m open to:
- Vulnerability research collaborations
- Kernel security discussions and code review
- Offensive security consulting engagements
- CTF team invitations and writeup exchanges
- Speaking at security conferences or community events
- Feedback on my published research or tools
I’m not the right contact for:
- Bug bounty handoffs on platforms I’m not registered on
- Generic “how do I get into hacking” questions — read the blog first
- Unsolicited recruiting without reading my work first
Where to Find Me
🐦 Twitter / X
The fastest way to reach me for quick exchanges, research discussions, or to just follow along.
🐙 GitHub
Where my tools and research code lives. Open issues on relevant repos for project-specific questions.
✉️ Email
For serious inquiries — consulting, collaboration proposals, or vulnerability disclosures.
PGP key available on request. For sensitive disclosures, always encrypt.
Vulnerability Disclosures
If you’ve found something and want a second pair of eyes, or you want to discuss responsible disclosure on a finding — email is the right channel. I take security research seriously and will respond thoughtfully.
Please include:
- Affected software and version
- Reproduction steps or PoC
- Your timeline expectations
Response Time
I read everything. I don’t always reply fast — kernel debugging doesn’t pause for notifications. But if your message is worth a response, it will get one.
Average response time: 24–72 hours depending on current research load.