LLMs turn old-school Burp Spider workflows into a mess of prod-db mistakes
rez0__ · x · 2026-07-23
The post jokes that when you mix LLMs into old-school Burp Spider-style security work, the problems become a weird blend of scope issues, state-changing actions in production banking databases, and a flood of support tickets.
The point is not a polished demo but a practical reminder: LLMs can make offensive security workflows more chaotic, especially when they start touching real systems.
More from coding & agent
- Sharing a One-Shot Prompt to Build a Local, Private Coding Agent UI for Pi — carsonfarmer · 2026-07-23
- Non-devs should buy Claude Code or Codex themselves, says a reposted tip — HankYeomans · 2026-07-23
- LangChain says the real agent problem is loop engineering, not just execution — LangChain · 2026-07-23
- Moving execution authority out of LLMs with schema-based validation — Jay299792458 · 2026-07-23
- Teaser: Orchestrator System with Dynamic Multi-Model Routing and Task Splitting — omarsar0 · 2026-07-23
- Reddit asks how to manage email identity for AI agents — BlakSavageGaming · 2026-07-23