>_

IsiraAdithya

Cyber Security Researcher
Ethical Hacker · Bug Bounty Hunter

Exploring systems. Breaking assumptions. Documenting the overlooked.

View profile

Portfolio Terminal

isira@portfolio:/surface
bash
isira@portfolio:~/surface$

Surface

One small command blooms into the work.

Live findings tape

Research, speaking, and public proof of work.

A quiet stream of the work that can be shared publicly. Private reports and sensitive details remain off the tape.

02 Research

XSSpecter

A modular framework that connects blind-XSS discovery, uniquely tagged payloads, callback capture, forensic evidence, alerting, and structured reporting.

04 Research notes

Intigriti 1025 RCE Challenge

A controlled challenge analysis covering SSRF-assisted file access, upload validation, and command-execution reasoning.

Research archive lens

Move through the archive by artifact.

The lens surfaces papers, tools, notes, and labs without exposing private targets, payloads, or report material.

Open research archive
683 Intigriti submissions
442 Accepted reports
#12 Intigriti rank
42 HackerOne thanks
Critical Streak tier

Public stats cached · last sync Oct 25, 2026 16:00 UTC

Approach

Security research is pattern recognition under uncertainty.

I find security flaws before they become breaches, with a focus on web, API, and offensive security research.

Break assumptions

I look for places where systems trust user-controlled state, stale permissions, inherited behavior, or implicit identity.

Trace boundaries

Most meaningful bugs sit between components: browser and server, user and tenant, API and worker, cache and origin.

Document clearly

A good report should make the issue reproducible, explain impact, and reduce the time between discovery and fix.

Build tooling

When a pattern repeats, I turn it into a script, workflow, or research note so the next investigation starts sharper.

Contact

Have a security problem worth investigating?

Use the contact flow to start a private thread, and keep sensitive target names or exploit details out of the first message.

Get in touch