r/BugBountyNoobs

Sharing a workflow that worked for me. The retrieval layer involved is my own project, so mentioning that upfront.

Setup: I was testing an XSS on a target behind Cloudflare, and every payload I tried was getting blocked by the WAF.

This time, instead of manually digging through old writeups, I gave my agent access to a retrieval layer built on top of a corpus of web security research (Preview RAG). The agent queries it in plain language, gets back actual writeups with sources attached, and uses that context to generate and test payload variants. One of those variants eventually got through and the XSS fired.

I'm not claiming the bypass itself is novel. It may already exist in a public writeup somewhere. What mattered to me was the workflow: the agent wasn't limited to whatever happened to be inside its training data. It could pull in relevant prior research and iterate from there.

That's the main reason I built this in the first place. Models have a training cutoff, but WAF evasion evolves quickly. Public bypasses get patched, new techniques appear, and the most useful information is usually the newest information. A retrieval layer helps bridge that gap.

The corpus is updated regularly and exposed over MCP, so it can be connected to any model with minimal setup, including smaller open-weight models.

Current limitations: it's strongest on client-side topics right now—XSS, WAF evasion, CSP, CORS, SSRF, request smuggling, and similar areas. Server-side coverage is improving, but still thinner, and it definitely won't have an answer for every problem.

Happy to share more about the setup. I'm honestly more interested in where this approach fails than where it succeeds. If you've experimented with agent-driven WAF bypassing and ran into hard limits, I'd love to hear about them.

Hey guys!

I've been using Notion for my writeups and notes for a while, and every time I tried to export or sync content programmatically, images were always broken. The official API gives you signed S3 URLs that expire in ~1 hour, so by the time your static site builds, half your images are dead.

So I built a small CLI tool that actually handles this properly, images get downloaded locally and the URLs get rewritten, so nothing breaks.

**What it does:**

- Pulls pages or entire databases as clean local markdown files

- Downloads images locally and rewrites the URLs (no more expiring links)

- Auto-detects your workspace and space ID

- Tracks sync state so it only re-pulls pages that actually changed

- Works with any stack - Astro, Hugo, Obsidian, whatever

**Setup is pretty simple:**

```

npm install -g notion-sync-cli

```

Add your Notion PAT to a `.env` file (Settings -> Personal access tokens, not integrations):

```

NOTION_TOKEN=ntn_xxxx

```

Then just run:

```

notion-sync init

```

It walks you through picking your database or pages interactively, no config file editing needed.

Package: `npm install -g notion-sync-cli`

GitHub: https://github.com/Chaelsoo/Notion-sync

Happy to answer any questions or take feedback.

built an MCP server that ships a "brain" per third-party API, stripe, resend, clerk, twilio, etc. each brain encodes bug patterns: symptom → likely cause → reproduce workflow → fix pattern. wanted to see if it actually catches real bugs vs just vibes.

so i made 5 small brownfield FastAPI apps, each with one planted bug:

- stripe: webhook dedup key on the wrong header. same event processed 2-3x on retry

- resend: handler only listens for email.delivered. bounces and complaints silently dropped, users stay "active" forever

- clerk: session token validation skipped on one endpoint

- agentmail: inbox webhook ignores message.received when body has attachments

- surge: SMS retry off-by-one re-sends to the wrong number

each app is 50-150 lines, .mcp.json wired. clone, run, point your agent at the dispatch prompt.

github.com/fetchsandbox/playground

two things i'm actually trying to figure out: does brain-as-yaml feel like the right curation level or too much vs lighter prompts? and how do you prove an agent fix actually worked when your test infra can't reach the handler?

honest negative findings are the most useful ones. already got one ("agent gave me a fake proof URL"), fixed it same day.