Security Research
Research is useful only when it is scoped, reproducible, and explainable. Each live engagement begins with written authorization; each CTF event follows its rules and challenge taxonomy. Public writeups are sanitized summaries of that process: evidence-aware, methodical, and written so another analyst can follow the reasoning chain from first signal to final report or solve.
RECON
Map the allowed surface, technology stack, and entry points. Anything outside written scope stays out of the work.
→
VALIDATE
Reproduce findings in a controlled, non-destructive way. Preserve enough requests, responses, screenshots, and notes for a defender to verify the issue.
→
DISCLOSE
Write the report with impact, reproduction steps, and remediation guidance. Publish only after the relevant disclosure rules allow it.
ENGAGEMENT SCOPE
IN SCOPE
- Bug bounty programs on authorized platforms
- CTF events and challenge infrastructure covered by event rules
- Web applications with an active, open bounty scope
- APIs and authentication flows listed in program rules
- Publicly accessible endpoints explicitly named in scope
OUT OF SCOPE
- Unauthorized systems or infrastructure
- Denial-of-service or load testing of any kind
- Social engineering against real employees
- Scope-adjacent targets not explicitly authorized
- CTF challenge flags, tokens, binaries, or private event artifacts
Available pages
Research
| # | Title | Date |
|---|---|---|
| 001 | WordPress Full Attack Chain — Lab Target (Phase 1-6) | 2026-05-21 |