API security testing - GraphQL, REST API, WebSocket, and Web-LLM attack techniques.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Offensive AI security testing and exploitation framework. Systematically tests LLM applications for OWASP Top 10 vulnerabilities including prompt injection, model extraction, data poisoning, and supply chain attacks. Integrates with pentest workflows to discover and exploit AI-specific threats.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
실행 점수 미검증
설치 방법 보기설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.
Test LLM applications for OWASP LLM Top 10 vulnerabilities using 10 specialized agents. Use for authorized AI security assessments.
1. Specify target (LLM app URL, API endpoint, or local model)
2. Select scope: Full OWASP Top 10 | Specific vulnerability | Supply chain
3. Agents deploy, test, capture evidence
4. Professional report with PoCs generated
Which file addresses which category is decided by
reference/catalog/llm-top10-2025.json, not by the
filename. The llmNN- prefixes on disk predate the 2025 renumbering and no longer match; the
content is correct, the labels were not. Cite an id only with its edition (LLM06:2025), because a
bare LLM06 means two different categories depending on which edition the reader assumes.
| Category | Attack surface |
|---|---|
LLM01:2025 Prompt Injection | Direct and indirect injection, instruction override, filter evasion |
LLM02:2025 Sensitive Information Disclosure | Training-data and cross-tenant RAG leakage, canary verification |
LLM03:2025 Supply Chain | Dependency CVEs, model provenance, malicious serialized models |
LLM04:2025 Data and Model Poisoning | Backdoor triggers, membership inference, behavioural anomalies |
LLM05:2025 Improper Output Handling | Code/XSS injection downstream, unsafe deserialization |
LLM06:2025 Excessive Agency | Tool/plugin abuse, privilege escalation, unauthorised actions — the category that matters for agents rather than chatbots |
LLM07:2025 System Prompt Leakage | Gap — no playbook yet. See the catalogue: what the prompt contains is a separate finding from whether it can be extracted |
LLM08:2025 Vector and Embedding Weaknesses | RAG injection, retrieval manipulation, embedding inversion |
LLM09:2025 Misinformation | Hallucination and confidence manipulation where output is relied upon |
LLM10:2025 Unbounded Consumption | Token flooding, cost impact, and model extraction/theft (2025 treats extraction-by-query as a consumption problem) |
Two classes are testable but are not OWASP categories, so they carry local TX- ids rather than
an invented LLMnn: monitoring evasion / forensic gaps, and adversarial perturbation of non-text
input. tools/test_llm_numbering.py enforces that separation.
Full Assessment (4-8 hours):
- [ ] Reconnaissance
- [ ] Deploy all 10 agents
- [ ] Execute exploits
- [ ] Capture evidence
- [ ] Generate report
Focused Testing (1-3 hours):
- [ ] Select a category from the catalogue (LLM01:2025 .. LLM10:2025, or a TX- local class)
- [ ] Deploy agent
- [ ] Execute techniques
- [ ] Document findings
Supply Chain Audit (2-4 hours):
- [ ] Inventory dependencies
- [ ] Scan CVEs
- [ ] Test plugins/APIs
- [ ] Verify model provenance
Enhances /pentest with AI-specific testing:
Prompt Injection: Instruction override, system prompt extraction, filter evasion
Model Extraction: Query sampling, token analysis, membership inference
Data Poisoning: Behavioral anomalies, backdoor triggers, bias analysis
DoS: Token flooding, recursive expansion, context exhaustion
Supply Chain: CVE scanning, plugin audit, model verification
MCP Tool Abuse: MCP server inspectors/debuggers often expose /api/mcp/connect or similar endpoints that accept serverConfig with arbitrary command parameters — unauthenticated RCE. Check for MCP Inspector, MCP Playground, or any MCP debugging UI on non-standard ports (6274, 3000, etc.).
All agents collect: screenshots, network logs, API responses, errors, console output, execution metrics.
Automated reports include: executive summary, detailed findings (CVSS scores), PoC scripts, evidence, remediation guidance.
/pentest skill for comprehensive security testing/AGENTS.mdreference/llm0X-*.md아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.
로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.
아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.
API security testing - GraphQL, REST API, WebSocket, and Web-LLM attack techniques.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Stitches confirmed single-asset findings into multi-hop attack paths across the organization. Builds a graph where nodes are assets and edges are confirmed exploit hops citing the findings that enable them.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Acquire an authenticated session THROUGH MFA/OTP on an in-scope target and emit a reusable session artifact (Playwright storageState + Bearer) so executors can test the post-auth attack surface. Use when the highest-value authenticated classes (BOLA/IDOR/mass-assignment/injection on the real data APIs) are blocked because login is gated by SMS-OTP or TOTP MFA. Distinct from the authentication skill (which ATTACKS auth); this one legitimately authenticates and hands the session to the rest of the engagement.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Authentication security testing - auth bypass, JWT attacks, OAuth flaws, password attacks, 2FA bypass, CAPTCHA bypass, and bot detection evasion.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Smart contract security testing and blockchain CTF exploitation. Covers Solidity vulnerability analysis, EVM storage manipulation, delegatecall attacks, CREATE/CREATE2 address prediction, and common DeFi exploit patterns. Use when analyzing Solidity contracts, solving blockchain challenges, or testing smart contract security.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Client-side vulnerability testing - XSS (reflected/stored/DOM), CSRF, CORS misconfiguration, Clickjacking, DOM-based attacks, and Prototype Pollution.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.