본문으로 건너뛰기
cccskills
무료GitHub에 공개

llm-redteam

LLM application red-teaming — prompt injection (direct + indirect), jailbreak, system-prompt leak, data exfiltration, guardrail bypass, multi-turn crescendo, cross-lingual + cipher + invisible-unicode token smuggling, excessive agency / tool abuse, insecure output handling. Canonical OWASP LLM Top 10 + ASI01-ASI10 mapping. Use when a target exposes a chat/completions/assistant/copilot endpoint, an AI feature that consumes user text or documents, or any /v1/chat, /api/chat, /mcp surface.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

설치 방법 보기

포함된 파일(1)

  • SKILL.md6.4 KB

SKILL.md(원문)

설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.

LLM Red-Team

Reflection is not exploitation. A model that echoes your payload is noise; a model that acts on it — leaks its system prompt, emits your canary, calls a tool, renders raw HTML downstream — is a bug. Prove the action, then chain it to concrete impact.

This is the first-class LLM-attack skill. The scanner behind it is tools/llm_redteam.py (canary-based corpus runner, /llm-redteam). For auditing an MCP server, use skills/mcp-server-audit; for attacking a deployed agent black-box, use skills/agentic-app-audit.

0. QUICK KILL CHECKLIST

Kill the lead (classify Informational, move on) when:

  • The model refuses and no canary / leak / tool-call ever lands. "It said something edgy" is not a finding.
  • System-prompt "leak" is just generic assistant boilerplate ("I am a helpful assistant"), not the target's actual instructions.
  • Prompt injection fires but reads/changes nothing the current user couldn't already access (no cross-tenant data, no tool with impact).
  • Output looks like XSS but the host app escapes it before rendering (check the actual downstream sink, not the chat response).
  • Exfil payload is a markdown image beacon but the client never fetches remote images.

1. ROUTING TABLE — signal on target -> what to run

SignalRun
Any chat/assistant endpointtools/llm_redteam.py --url <endpoint> --field <json-field> (full corpus)
OpenAI-style API--template '{"messages":[{"role":"user","content":"{{PAYLOAD}}"}]}' --response-path choices.0.message.content
Only want one class--category jailbreak (see --list-categories)
Uploads/RAG/"summarize this doc"indirect-injection + token-smuggling (invisible unicode in the doc)
Agent has toolsexcessive-agency category + skills/agentic-app-audit
Confirm blind exfilplant a canary host, correlate with tools/oob_listener.py

2. ATTACK CLASSES (corpus categories)

The runner fires a canary per run (RT_PWNED_xxxx); a category "lands" when the canary / a real leak / a tool-call shows up in the response.

  • prompt-injection — direct instruction override, delimiter breaks.
  • jailbreak — DAN / developer-mode persona escape.
  • system-prompt-leak — repeat-above, keyword-anchor, scenario-escape.
  • data-exfil — markdown-image beacon / canary emission to an attacker host.
  • indirect-injection — payload framed as a retrieved document / tool result (the high-value one for RAG apps).
  • guardrail-bypass — base64 / split-string instruction smuggling.
  • multi-turn-crescendo — single-shot simulation of a gradual escalation jailbreak.
  • cross-lingual — override instruction in another language to dodge English-only filters.
  • cipher-obfuscation — leetspeak / ROT13-wrapped instruction.
  • token-smuggling — invisible "Sneaky Bits" unicode (U+2062/U+2064) carrying a hidden instruction (shared encoder with tools/hai_payload_builder.py).
  • excessive-agency — coerce an unsafe tool call / exfil (SSRF via "fetch URL", email send, payment).
  • insecure-output — get the model to emit raw HTML/script that a downstream sink renders (XSS via AI).

3. CANONICAL OWASP ASI01-ASI10 (single source of truth)

This table is the ONE authoritative ASI mapping for the whole toolkit — skills/bug-bounty and skills/web2-vuln-classes both defer to it. If you edit the taxonomy, edit it here.

IDClassWhat to testChain to
ASI01Prompt Injection / Goal HijackOverride objectives via direct or indirect injectionIDOR / exfil / tool abuse
ASI02Tool MisuseAttacker-controlled tool params ("fetch this URL", code tool)SSRF / RCE
ASI03Privilege CompromiseAgent uses broader perms / admin tokens than the userPriv-esc / cross-tenant
ASI04Supply ChainCompromised plugin / MCP server / tool-output poisoning next agentRCE / data theft
ASI05Code ExecutionUnsafe code-interpreter / sandbox escapeRCE
ASI06Memory & Context PoisoningPersistent RAG/memory corruption across sessions/usersStored injection affecting all users
ASI07Agent CommunicationInter-agent spoofing / IDOR (agent A reads agent B's context)Cross-tenant disclosure
ASI08Excessive AgencyDestructive action without confirmation; cascading failuresFunds/email/delete
ASI09Insecure Output HandlingAI output rendered as XSS / SQLi / command injection downstreamXSS / injection
ASI10Sensitive Information DisclosureLeaks system prompt / keys / configs / user dataSecrets -> deeper access

Triage rule: ASI alone = Informational. It is a bounty only when chained to IDOR / exfil / RCE / ATO with a working PoC.

4. CHAIN TO IMPACT (what makes it payable)

StandaloneChainResult
Prompt injection+ reads another user's conversation/data (IDOR)High
Indirect injection (RAG doc)+ persists in memory -> hits every userHigh/Critical
Tool misuse "fetch URL"+ hits internal service / IMDS and returns dataSSRF (Medium/High)
Insecure output+ the host renders it -> stored XSS -> session theftHigh
System-prompt leak+ the prompt contains an API key / internal URLHigh
Excessive agency+ unconfirmed destructive action (send funds, delete)High/Critical

5. CONFIRMATION DISCIPLINE (no false positives)

  • A category only counts when the canary / real leak / tool-call is observed in the response — never on "it sounded compliant."
  • For blind exfil, require a correlated out-of-band callback (tools/oob_listener.py), not just a rendered beacon tag.
  • For insecure-output XSS, confirm execution at the downstream sink with the XSS verifier (tools/verifiers/xss.py / tools/dom_xss_harness.py), not in the chat reply.
  • Record the exact payload + response excerpt; the report must be reproducible verbatim.

리뷰

아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.

댓글

로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.

아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.

보내면 바로 공개됩니다. 이메일 주소나 전화번호 같은 개인 정보는 쓰지 마세요. URL은 2개까지입니다.

0 / 1,000자

이 양식은 reCAPTCHA로 보호되며 Google 개인정보처리방침 및 서비스 약관이 적용됩니다.

같은 저장소의 스킬

Black-box security audit of a DEPLOYED AI agent (not the MCP server behind it) — tool-call hijacking, cross-session memory poisoning, confused-deputy via connected tools, agent-to-agent IDOR, excessive agency / unconfirmed destructive actions, and privilege compromise where the agent holds broader perms than the user. Use when the target is a live assistant/agent product with tool access (bookings, email, payments, file/RAG, browsing) rather than a raw LLM chat box or an MCP server you can read.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

awarexone/Agentic-Bug-Hunter5.4천2026년 10월 10일 업데이트

argus

무료

Argus — the all-seeing scanner suite. Six automated scanners for high-value web + LLM bug classes — CORS misconfiguration (origin reflection / null / credentialed read), CRLF & host-header injection, NoSQL injection (operator auth-bypass / $where blind), JWT attacks (alg:none / RS256→HS256 confusion / secret crack), out-of-band confirmation of blind SSRF/XXE/SQLi/RCE/Log4Shell via interactsh, and an LLM red-team corpus (prompt-injection / jailbreak / system-prompt leak / exfil / indirect injection). Use when a target exposes a JSON API, a login endpoint, JWT auth, a parameter that might reach the server, a chatbot/agent, or any endpoint suspected of a blind/out-of-band bug.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

awarexone/Agentic-Bug-Hunter5.4천2026년 10월 10일 업데이트

Use at the START of any bug bounty hunting session, when switching targets, or when feeling lost about what to do next. Master orchestrator that combines the 5-phase non-linear hunting workflow with the critical thinking framework (developer psychology, anomaly detection, What-If experiments). Routes to all other skills based on current hunting phase. Also use when asking "what should I do next" or "where am I in the process."

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

awarexone/Agentic-Bug-Hunter5.4천2026년 10월 10일 업데이트

Complete bug bounty workflow — recon, pre-hunt learning, vulnerability hunting (IDOR, SSRF, XSS, auth bypass, CSRF, race conditions, SQLi, XXE, file upload, business logic, GraphQL, HTTP smuggling, cache poisoning, OAuth, OIDC, SSTI, subdomain takeover, cloud misconfig, ATO chains, agentic AI), LLM/AI security testing (ASI01-ASI10), A-to-B bug chaining, bypass tables, language-specific grep patterns, and reporting (7-Question Gate, 4 validation gates, CVSS 3.1, PoC generation, submission checklist). Use for ANY bug bounty task — recon, hunting specific vulns, auditing source code, testing AI features, validating findings, or writing reports.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

awarexone/Agentic-Bug-Hunter5.4천2026년 10월 10일 업데이트

Complete bug bounty workflow — recon (subdomain enumeration, asset discovery, fingerprinting, HackerOne scope, source code audit), pre-hunt learning (disclosed reports, tech stack research, mind maps, threat modeling), vulnerability hunting (IDOR, SSRF, XSS, auth bypass, CSRF, race conditions, SQLi, XXE, file upload, business logic, GraphQL, HTTP smuggling, cache poisoning, OAuth, timing side-channels, OIDC, SSTI, subdomain takeover, cloud misconfig, ATO chains, agentic AI), LLM/AI security testing (chatbot IDOR, prompt injection, indirect injection, ASCII smuggling, exfil channels, RCE via code tools, system prompt extraction, ASI01-ASI10), A-to-B bug chaining (IDOR→auth bypass, SSRF→cloud metadata, XSS→ATO, open redirect→OAuth theft, S3→bundle→secret→OAuth), bypass tables (SSRF IP bypass, open redirect bypass, file upload bypass), language-specific grep (JS prototype pollution, Python pickle, PHP type juggling, Go template.HTML, Ruby YAML.load, Rust unwrap), and reporting (7-Question Gate, 4 validation gates, human-tone writing, templates by vuln class, CVSS 3.1, PoC generation, always-rejected list, conditional chain table, submission checklist). Use for ANY bug bounty task — starting a new target, doing recon, hunting specific vulns, auditing source code, testing AI features, validating findings, or writing reports. 中文触发词:漏洞赏金、安全测试、渗透测试、漏洞挖掘、信息收集、子域名枚举、XSS测试、SQL注入、SSRF、安全审计、漏洞报告

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

awarexone/Agentic-Bug-Hunter5.4천2026년 10월 10일 업데이트

CI/CD pipeline security hunting — GitHub Actions workflow injection, secret exfiltration, self-hosted runner poisoning, dependency confusion, OIDC token theft, and supply chain attacks. Covers sisakulint scanning, manual workflow analysis, and chaining CI/CD bugs into critical findings. Use when a target has public repos, GitHub Actions, CircleCI, Jenkins, or GitLab CI.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

awarexone/Agentic-Bug-Hunter5.4천2026년 10월 10일 업데이트

awarexone의 스킬 모두 보기

이 스킬의 문제 신고