August 26, 2026
— without spending a dollar.
The first time I found an unauthenticated ComfyUI instance sitting on a public IP, rendering someone’s custom AI videos without a password…

By 👻 GhostZA (ကိုကျော်)
2 min read
— without spending a dollar.
The first time I found an unauthenticated ComfyUI instance sitting on a public IP, rendering someone's custom AI videos without a password — I almost closed my laptop and walked away.
It was too easy. No exploit. No CVE. Just… open.
Three years later, I've mapped thousands of similar instances across hundreds of platforms. This is the workflow I use, the tools I rely on, and the lessons I've learned along the way.
I'm not a company. I don't sell courses. I don't run a "consulting firm." I'm one person in Yangon with a fiber connection and too much free time.
This is what I actually do.
Why AI Platforms Are a Goldmine (Right Now)
AI is the fastest-growing attack surface in 2026. Every week, dozens of new AI startups ship a product built on:
- Next.js + Supabase (anon key in the JS bundle)
-
- Python FastAPI + an open port
-
- Jupyter / MLflow / Gradio left exposed
-
- Stripe Checkout with race conditions in the refund flow
-
- LangChain agents with prompt injection everywhere
The developers are brilliant. They're building faster than any security team can keep up with. That's not their fault — that's the gap I live in.
My Default Recon Stack (All Free, All Open Source)
I don't have a Burp Pro license. I don't need one.
- Discovery:*
-
- FOFA (Chinese equivalent of Shodan) — free tier covers my needs
-
- SearXNG (self-hosted meta search) — no rate limits, no API keys
-
- GitHub dorks — most startups leak their keys in their first commit
- Verification:*
-
- Playwright (headless Chromium) — for authenticated probing
-
- curl + custom Python scripts — for API surface mapping
-
- Tor — for the actual extraction phase
- Output:*
-
- A single markdown file per target with the full kill chain
-
- Screenshots at every step
-
- Reusable PoC scripts that I publish on GitHub later
That's it. No Splunk. No Tenable. No enterprise nonsense.
The 5 Patterns I Find Every Week
After thousands of probes, I've narrowed it down to five recurring patterns:
1. The "Anonymous Supabase" Leak
Startup builds with NEXT_PUBLIC_SUPABASE_ANON_KEY=... in their client bundle. RLS is set on most tables — but not all. One forgotten users table with auth.role() = 'anon' read access = the entire database.
2. The ComfyUI on Port 8188
Someone runs ComfyUI with --listen 0.0.0.0 --enable-cors-header * for "remote access." Now anyone on the internet can submit prompts on their GPU.
3. The Stripe Refund Race
Checkout flow charges once. Refund webhook processes async. Submit 5 simultaneous refund requests = 5x your money back before the order even clears.
4. The Unauthenticated Admin Panel
Build an admin dashboard. Forget the auth middleware. Expose it at /admin. The internets finds it in 6 hours.
5. The MCP Server with --no-auth
Model Context Protocol servers are the new hotness. Some ship with default config that lets any client connect — and most of them have shell access.
I have working PoCs for all five. I publish them on GitHub under kokyaw-gza/ when I have time. The goal isn't the loot — it's making sure the vendor patches it.
My Disclosure Ethic
I'm not in this for "bounties." I disclose to vendors when:
- The platform is small (< 100K users)
-
- The vendor has a public security contact
-
- The fix can be shipped in < 30 days
For big platforms (the FAANG-tier), I keep the methodology public and the specifics private. If I find a €300 credit forge on a major AI platform, I don't post the exact RPC endpoint — I post the pattern. Vendors fix the class of bug, not just my instance.
This keeps me out of jail and keeps the vendors honest. Win-win.
What's Next
I'm going to start publishing my toolset on GitHub over the coming weeks:
supabase-rls-probe— auto-mass-scan for anon-key RLS leaks-
comfyui-unauth-reaper — find + report exposed ComfyUI instances
-
ai-platform-recon— the all-in-one recon framework I actually use
-
stripe-race-finder— generic payment race-condition detector
If you find my work useful, follow me here. Or check the GitHub: github.com/kokyaw-gza
I'm one person. I'm not fast. But I find things.
— -
- 👻 GhostZA — Yangon, Myanmar. Independent. Anonymous by design.*