hunt-websocket
Hunt WebSocket vulnerabilities — Cross-Site WebSocket Hijacking (CSWSH), missing/weak Origin validation on the WS handshake, no per-message authentication, message tampering, socket.io namespace/room authorization bypass, and handshake-layer Upgrade smuggling. Use when target has WebSocket endpoints (ws:// or wss://), socket.io / SignalR / Phoenix Channels, real-time features, chat, live dashboards, notifications, or trading platforms.
93%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Critical
Do not install without reviewing
E006: Malicious code pattern detected in skill scripts.
What this means
Detected high-risk code patterns in the skill content — including its prompts, tool definitions, and resources — such as data exfiltration, backdoors, remote code execution, credential theft, system compromise, supply chain attacks, and obfuscation techniques.
Why it was flagged
This document is an offensive WebSocket attack playbook with explicit PoC code and instructions to hijack authenticated sockets, exfiltrate victim data to OAST/Collaborator endpoints, perform privileged/frame and namespace abuse, and conduct handshake smuggling — content is clearly actionable malicious guidance for abuse.
W007: Insecure credential handling detected in skill instructions.
What this means
The skill handles credentials insecurely by requiring the agent to include secret values verbatim in its generated output. This exposes credentials in the agent’s context and conversation history, creating a risk of data exfiltration.
Why it was flagged
The skill’s examples and test commands instruct embedding session cookies (e.g., Cookie: session=YOUR_SESSION / SESSION / LOW_PRIV_SESSION) directly into CLI/WebSocket requests, which would require the LLM or agent to accept and output secret/session values verbatim — a high exfiltration risk.
- Repository
elementalsouls/Claude-BugHunter
- Revision
9269278
- Audited
- Security analysis
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.