xiety@void:~$
Self-taught, self-driven. For six-plus years I've found vulnerabilities from low to critical in some of the largest companies on the planet — web and binary. I live in the gap between how a system is documented to work and how it actually works: map every function, learn exactly what it assumes, then break those assumptions one by one until the whole thing falls open.
I'm a self-taught penetration tester and bug bounty hunter with 6+ years of hands-on offensive work against some of the largest corporations in the world. No bootcamp, no handed-down playbook — just an obsession with taking a system apart to understand it, and the stubbornness to keep pulling threads until something gives.
I find bugs across the whole severity range, from low to critical, and across the whole stack. Most of my work is complex logic flaws: a race condition in a payment flow, an OAuth dance that trusts one parameter too many, an authorization check that exists on nine endpoints and is missing on the tenth. But I don't stop at the web — recently I found a heap overflow in Apple software, reported it through coordinated disclosure, and confirmed it fixed in an upcoming release.
My work spans banks, payment rails, national trust services, healthcare platforms, government infrastructure and critical logistics. The targets are redacted here, but the pattern isn't: find the one function everyone assumed was safe, figure out exactly what it trusts, and demonstrate — end to end — what happens when that trust is misplaced.
Every finding below was responsibly disclosed through coordinated bug bounty and VDP channels. Proofs-of-concept, target names and reproduction details are permanently withheld.
Distribution of vulnerability classes across 137 documented findings. Many findings chain multiple classes, so categories overlap — the shape shows where I spend my time: identity, authorization, and the logic that governs both.
A selection of validated findings. Target identities, domains, payloads and reproduction steps are [REDACTED] — what remains is the shape of the flaw and the impact. Each was reported through a coordinated channel and fixed.
| Vulnerability Class | Count | Weight | Top Severity |
|---|
* counts overlap where a single finding chains multiple classes. 27 Critical · 41 High · 69 Medium across 40 programs.
Platform achievements earned for sustained, high-impact research — consistency over years, max-reward findings, and long submission streaks.





Available for offensive security engagements, penetration testing, bug bounty collaboration and security research. If it has an auth flow or a business process, I want to break it — with permission.