Fray
Vibe security — AI-native intelligence & testing.
Target Intelligence — identify who an attack surface belongs to and reach the right security team for responsible disclosure. Plus a zero-config CLI scanner: recon, 7,800+ payloads, 98 WAF vendors.
pip install fray && fray go target.com # scan only targets you are authorized to test
Docs · Discussions · dalisec.io
🌐 English | 日本語
FOR AUTHORIZED SECURITY TESTING ONLY — Only test systems you own or have explicit written permission to test.
Before Fray vs. With Fray
| Traditional | With Fray |
|---|---|
| Install 5+ tools (nmap, wafw00f, sqlmap, nikto, nuclei) | pip install fray |
| Learn each tool's flags and config formats | fray go target.com |
| Manually correlate findings across tools | Automatic: recon → test → report |
| Write scripts to chain tools together | 42 checks · 12 deep scan modules · 7,800+ payloads |
| Security expertise required | Built for anyone who ships web apps |
What's New — v3.5.6
fray analyze— per-pattern WAF bypass table. Confirms which payload patterns are blocked, then finds what gets through — with injection mechanics explaining why each bypass works- 42 recon checks — CVE probes for Next.js, Log4Shell, Spring4Shell, WordPress, Drupal fire automatically based on detected tech stack. No manual configuration
- 18 vendor feeds — Unit 42, F5 Labs, Cloudflare, Imperva, PortSwigger, MSRC Patch Tuesday + 12 more.
fray feed --auto-addpulls, validates PoC accuracy, and stages payloads fray vendor-intel— latest CVEs and posts from all 18 feeds in one terminal view- Wappalyzer — 3,920 tech patterns from npm. Detects Shopify, EC-CUBE, Vercel, Datadog, Auth0, Kong, 4,200+ technologies from response headers, cookies, and scripts
- Report — security grade A–F with specific improvement steps, RDAP domain age, origin cloud provider (GCP/AWS/Azure), VPN CVEs in Known Vulnerabilities
Core Commands
fray go <url> # ★ Full pipeline: recon → test → report (start here)
fray recon <url> # 42-check reconnaissance — WAF, TLS, CVEs, secrets, subdomains
fray test <url> --smart # Smart payload selection from recon findings
fray analyze <url> # Per-pattern WAF bypass analysis with bypass table
fray detect <url> # WAF/CDN fingerprint (98 vendors)
fray harden <url> # OWASP hardening audit (A–F grade)
fray vendor-intel # Latest CVEs from 18 security vendor feeds
fray feed --auto-add # Pull CVEs → validate PoC → update payload DB
fray smoke --local # Test detection accuracy against localhost Docker lab
fray dashboard # Web UI — timeline, diff, live reload
fray mcp # MCP server for Claude / ChatGPT / Cursor
fray <url> is a shortcut for fray go <url>.
Who It's For
- Developers — run
fray gobefore launch. Done. - Bug bounty hunters — 7,800+ payloads, WAF bypass intelligence, adaptive cache learns across scans.
- Pentesters — 12 deep scan modules, stealth mode, auth support, per-pattern bypass analysis.
- DevSecOps — GitHub Action, SARIF output,
--jsonfor pipelines. - Security teams — MCP server for AI agents, VS Code extension, 18 live threat intel feeds.
Payload Coverage
7,800+ payloads across 43 categories:
| Category | Count | Category | Count |
|---|---|---|---|
| XSS | 1,329 | AI/LLM Prompt Injection | 410 |
| Web Shells | 994 | Path Traversal | 293 |
| WordPress | 964 | SQL Injection | 258 |
| LLM Testing | 740 | Command Injection | 233 |
| Other / Generic | 368 | SSTI | 220 |
| CSP Bypass | 177 | XXE | 178 |
| Modern Bypasses | 137 | API Security | 130 |
| SSRF Cloud Metadata | 123 | Prototype Pollution | 110 |
| CRLF Injection | 94 | Open Redirect | 91 |
| LDAP Injection | 90 | XPath Injection | 89 |
| JWT Attack | 32 | Supply Chain | 46 |
| Auth Bypass | 20 | GraphQL Attacks | 24 |
| Cache Poisoning | 20 | Deserialization | 16 |
| Mass Assignment | 25 | Race Condition | 16 |
| RAG Security | 16 | HTTP Smuggling | 17 |
| Host Header Injection | 15 | CORS | 15 |
MCP — AI Agent Integration
18 tools via MCP for Claude, ChatGPT, Cursor, and any MCP client.
pip install 'fray[mcp]'
{ "mcpServers": { "fray": { "command": "python", "args": ["-m", "fray.mcp_server"] } } }
Ask "What XSS payloads bypass Cloudflare?" — suggest_payloads_for_waf, generate_bypass_strategy, analyze_response, hardening_check, and 14 more tools run directly.
Claude Code guide → · ChatGPT guide →
CI/CD — GitHub Action
# .github/workflows/waf.yml
- uses: dalisecurity/fray@v1
with:
target: https://staging.example.com
categories: xss,sqli
Exits non-zero on bypass findings. Integrates with GitHub Security tab via SARIF. CI/CD guide →
Auth & Stealth
fray test https://target.com --cookie "session=abc123"
fray test https://target.com --bearer eyJhbG...
fray test https://target.com --stealth -d 0.5 # randomized UA + jitter
fray recon https://target.com --scope scope.txt # in-scope enforcement
Community
- Discussions — questions, ideas, show what you built
- Issues — bugs and feature requests
- Contributing — PRs welcome. For AI coding agents, see AGENTS.md
- VS Code Extension —
MIT License · Only test systems you own or have explicit authorization to test · Security issues: soc@dalisec.io
dalisec.io · Built by hunters. For defenders.
1 maintainer
Metadata
1 maintainer
Release files for fray 3.5.240
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| fray-3.5.240.tar.gz | 1.5 MB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| fray-3.5.240-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 3.0 MB
Release files / fray-3.5.240.tar.gz
| Download URL | fray-3.5.240.tar.gz |
|---|---|
| Size | 1.5 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
b179f352c6253ef2ecd95835e186d57f3647d03d2c2c04049e8d1eed1df5311f
|
|
BLAKE2b-256 checksum How to use checksums |
c0b41b5ffe60e0b06227230da6e1d38e6715a43bc40c8004aa3d944939f09c6b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 12, 2026.
Transparency logRelease files / fray-3.5.240-py3-none-any.whl
| Download URL | fray-3.5.240-py3-none-any.whl |
|---|---|
| Size | 1.5 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
ba4ac95e2b9e552d7034ad4c3b49c1e7c7d29fb7e56dbbf8a161ccf10563150f
|
|
BLAKE2b-256 checksum How to use checksums |
ff64e7f144a8bd2ea81f57183f88e4f6eb254d7e05dc92673b6aab46cf071797
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 12, 2026.
Transparency logSecurity for fray 3.5.240
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for fray-3.5.240.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 12, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
