Public HackerOne disclosure
A disclosed report involving exposed test/integration API behavior, linked only because it is already public.
HackerOne report #745171Work
Bug bounty profiles and public platform signals.
Public profile links are listed directly. Private reports, program names, and sensitive bounty details stay off the site.
Profiles
Live bug bounty stats.
Public aggregate signals from each platform, synced automatically. Private report and program details stay off the site.
intigriti@profile ~ $ stats
Rank #12
8,696
reputation
683
submissions
442
accepted
Streak tier
Critical
219 pts · 90d
Valid ratio97.9%
hackerone@profile ~ $ stats
89th · impact
1,491
reputation
42
thanks
12
badges
5.5
signal
Signal80th
Impact89th
Public stats · synced Oct 25, 2026 16:00 UTC
Selected work
Public findings and privacy-safe case studies.
Published material links to its source. Confidential work is reduced to vulnerability class, impact boundary, and method.
Authorization bypass in multi-tenant API
Private disclosure. Rendered as an abstracted case study to avoid exposing target or report details.
Private program · Impact confirmedMy first bug - Reflected XSS
A personal writeup about early bug bounty learning and reflected XSS discovery.
blog.isiraadithya.comIntigriti 1025 RCE Challenge
Challenge writeup with a controlled research target and public-safe technical detail.
Intigriti challengeBurp match and replace workflow
A practical note on shaping requests during web security testing workflows.
Intigriti tipSecurity assessment for production web/API surface
Confidential engagement. Shown only as category-level experience without target, exploit, or client identifiers.
Confidential · Web and API