~ / contact
Open a channel
Consulting, research collaboration, or a second opinion on an architecture decision. Short, specific messages get faster replies.
contact@th333boo.com
Response
Between engagements, usually within two working days
Engagements
Private sector and government-level programmes; remote-first, travel by arrangement
Scope
Signed rules of engagement before any testing begins
Email is the front door. Telegram is faster if something is already on fire — use it for coordination, not for dropping sensitive material.
Government-level programmes are welcome too: same rules, more paperwork.
Before you send
A useful first message answers four things:
- What the system does — product, internal tool, infrastructure, mobile app.
- What worries you — a suspected hole, an architecture review, a compliance deadline, a post-incident cleanup.
- Timeline — when it needs to be done, and what happens if it isn’t.
- Constraints — rules of engagement, regulated data, change freezes, existing vendors.
No NDA is needed for a first conversation. Happy to sign a mutual one before details get specific.
Channels
- Email contact@th333boo.com
- Telegram @th333boo3
- LinkedIn /company/th333boo
Ground rules
Don’t send credentials, customer data, or exploit code in a first message. If this is an active incident, put INCIDENT in the subject line and ping Telegram — we’ll set up an appropriate channel before anything sensitive moves.