Bug Bounty
Recon workflows, testing methodology, notes, and lessons from authorized programs.
Explore methodology →
CYBERSECURITY
Bug bounty research, custom tooling, writeups, and authorized offensive-security experiments.
BUG BOUNTY JOURNEY
The public profiles and repositories behind the Dreams of Tragedy security work.
FOCUS AREAS
Recon workflows, testing methodology, notes, and lessons from authorized programs.
Explore methodology →Custom Burp extensions, scanners, automation helpers, and purpose-built research utilities.
View featured tools →Technical notes, discoveries, methodology breakdowns, and public research.
Read latest posts →Experiments, works in progress, test environments, and ideas still being refined.
View active labs →FEATURED TOOLS
A growing set of helpers built around real testing and research needs.
A Burp Suite extension that scans textual Proxy responses for DOM source indicators and exports findings for review.
A personal SSRF scanning and workflow framework for authorized testing and research.
Checks for reflected parameters and collects them into a list for review and export.
An offline SIEM query builder for Splunk, CrowdStrike, Microsoft Sentinel, and IBM QRadar, with IOC searches, visual filters, and customizable result tables.
FEATURED PROJECT
Automatically surface DOM source indicators from Burp Proxy traffic so interesting client-side attack surfaces are easier to review.
Sources
location.search
location.hash
document.URL
window.name
Review proxy responses
Collect matches
Export findings → CSV
RECON METHODOLOGY
The goal is not to collect the biggest URL list. It is to understand functionality, prioritize attack surface, and use each finding to guide the next round of recon.
Build a clean scope, enumerate subdomains, normalize results, and flag higher-value hosts such as API, admin, staging, auth, upload, webhook, GraphQL, legacy, and backup systems.
Resolve hosts, probe HTTP services, retain interesting status codes, and classify frameworks, CMSs, web servers, CDNs/WAFs, authentication systems, APIs, cloud providers, and JavaScript frameworks.
Browse manually through Burp, crawl important applications, compare current and historical endpoints, and inventory parameters, APIs, JavaScript, uploads, redirects, webhooks, GraphQL, and WebSockets.
Look for hidden functionality, routes, source maps, internal hosts, storage buckets, OAuth endpoints, file-processing paths, redirects, URL-fetching behavior, and structured API operations.
Prioritize dynamic endpoints for hidden-parameter discovery and use technology-specific content discovery instead of blindly fuzzing every host the same way.
Classify what an endpoint actually does—fetch, redirect, upload, download, import, webhook, object access, OAuth, GraphQL—and map that behavior to the bug classes that make sense.
Branch into focused testing only after recon produces a plausible hypothesis, with special attention to URL processing, client-side behavior, and authorization boundaries.
Prioritize the highest-value functionality first, then feed every new host, route, parameter, or behavior discovered during testing back into recon.
THE LOOP
If testing reveals new information, it goes straight back into recon. The process keeps moving until the target stops producing useful new attack surface.
RECENT POSTS
This area will hold public writeups, methodology notes, and lessons learned.
ACTIVE LABS
Experimental helpers, workflow improvements, and research prototypes will appear here as they mature.