Offensive Web Application Security Software

Joined May 2018
161 Photos and videos
Pinned Tweet
Burp Bounty Pro v3.1.0 is out. New: AI Scanner. Sends each request to an LLM with structured context extracted from the response. The AI decides which profiles to launch automatically. A new option alongside Active Scan and Smart Scan, not a replacement.
2
25
132
10,969
Last week we asked if an MCP server for Burp Bounty Pro would be useful. The answer was clear: yes. So we're building it.
2
1
7
687
Connect an AI agent to BBP: launch scans, pick profiles by tag, read findings, trigger Smart Scan rules. The principle we won't break: deterministic control. The agent decides what to scan, the programmatic engine executes with the same precision Thanks to everyone.
2
510
Bounty Security retweeted
An LLM's output is not trustworthy by default: it must be treated as unverified data, just like input from any user. If you don't validate it before displaying or executing it, that's Insecure Output Handling.
1
3
3
251
Thinking about an MCP server for Burp Bounty Pro. Let an agent drive it: "scan this host for SQLi SSRF, summarize by severity" and BBP runs end to end. Genuinely undecided. If you use the tool, your take shapes this one ๐Ÿ‘‡
1
2
5
338
We broke down the 6 new AI/LLM profiles in Burp Bounty Pro: ๐Ÿ” Response headers โ†’ model provider ๐ŸŒ Gateway fingerprints โ†’ proxy mesh โค๏ธ Health/metrics โ†’ versions ๐Ÿ“ฆ JSON metadata โ†’ RAG, MCP ๐Ÿค– OpenAI-compatible โ†’ raw LLM endpoint โฑ๏ธ RateLimit โ†’ Denial of Wallet
4
1
7
647
Browse the target. By the time you've mapped it, BBP has told you: Kong-fronted service routing GPT-4o through a Pinecone RAG pipeline, MCP tools attached, rate-limited by tokens. ๐ŸŽ 15 days free โ†’ bountysecurity.ai/pages/contโ€ฆ
550
Bounty Security retweeted
Some of the techniques emerging to improve the performance of LLMs are based on ideas borrowed from how the human brain works. In our latest post we sum up 5 of the most recent ones: kaptor.ai/blog/brain-based-lโ€ฆ
1
4
222
Profile 6, the last of the AI/LLM set in Burp Bounty Pro: RateLimit header disclosure. โฑ๏ธ Detects RateLimit-* and X-RateLimit-* headers. ๐ŸŽ 15 days free โ†’ bountysecurity.ai/pages/contโ€ฆ
2
3
458
Low limit on one route high on another โ†’ which endpoint hits the expensive model. Map the architecture by following the money. Denial of Wallet: exhaust the budget, not the compute. Exact limits tell you how
1
353
Profile 5 of the AI/LLM set in Burp Bounty Pro: OpenAI-compatible API fingerprinting. ๐Ÿค– Detects: chatcmpl-* completion IDs choices model usage objects in the body The OpenAI schema became the de facto standard. Detecting it = found an LLM endpoint.
3
1
563
It confirms a raw LLM API is reachable, not just a wrapped chat UI. Raw endpoints (self-hosted vLLM, Ollama) often have far fewer guardrails. The usage object even hints at how big the hidden system prompt is ๐ŸŽ 15 days free โ†’ bountysecurity.ai/pages/contโ€ฆ
1
377
Profile 4 of the new AI/LLM set in Burp Bounty Pro: AI metadata leakage in JSON bodies. ๐Ÿ“ฆ Detects in any response body: rag_enabled mcp_enabled embedding_model vector_db *_tokens model_provider service_version
2
1
3
497
Each field is part of the attack plan: rag_enabled โ†’ PoisonedRAG on the table mcp_enabled โ†’ tool poisoning on the table embedding_model โ†’ inversion attempts viable vector_db โ†’ know the retrieval backend ๐ŸŽ 15 days free โ†’ bountysecurity.ai/pages/contโ€ฆ
1
386
Bounty Security retweeted
Nearly every SOC we talk to is automating something with LLMs. L1 phishing triage, ticket classifiers, alert enrichment. And nearly all of them make the same two mistakes: secrets in the system prompt LLM output with no validation.
2
2
4
317
Profile 2 of the new AI/LLM set in Burp Bounty Pro: API gateway fingerprints. ๐ŸŒ Detects: x-kong-upstream-latency x-kong-proxy-latency x-kong-request-id x-envoy-upstream-service-time x-envoy-attempt-count x-envoy-original-path
2
2
6
475
The gateway is the map of the architecture. Kong โ†’ likely rate limiting and auth plugins. Envoy โ†’ service mesh microservices. Latency headers โ†’ where the LLM provider lives. Passive recon that changes the whole engagement ๐ŸŽ 15 days free โ†’ bountysecurity.ai/pages/contโ€ฆ
209
AI pentests are growing fast. The first step on any of them: figure out the model, the provider, the architecture. Profile #1 of 6 in the new AI/LLM set detects: ๐Ÿ” x-ai-backend ๐Ÿ” x-llm-provider ๐Ÿ” x-openai-model ๐Ÿ” x-anthropic-model ๐Ÿ” x-mcp-enabled ๐Ÿ” x-model
1
2
8
450
x-openai-model: gpt-4o โ†’ which prompt injection patterns to use x-mcp-enabled: true โ†’ tool poisoning attack surface exists x-anthropic-model: claude-sonnet โ†’ different guardrails to bypass Test it: burpbountylab.com/ ๐Ÿ‘‰ Burp Bounty Pro: bountysecurity.ai/pages/burpโ€ฆ

275
Just shipped 6 new passive profiles for Burp Bounty Pro, focused on AI/LLM disclosure surfaces: ๐Ÿ” AI/LLM response headers ๐ŸŒ Kong Envoy fingerprints โค๏ธ Health, status, metrics endpoints ๐Ÿ“ฆ AI metadata in JSON bodies ๐Ÿค– OpenAI-compatible API detection โฑ๏ธ RateLimit headers
2
2
3
387
Validate them on Burp Bounty Lab. Load Burp Bounty Pro with the new profiles, point at burpbountylab.com/, all 6 fire Start of an AI-focused profile set. Disclosure patterns you keep seeing in AI pentests? Drop them.

1
158