Skip to content
New

DeepSeek V4.1 Flash free for 7 days: 10M tokens a day after a top-up of $10 or more. Until Nov 30.

How it works
noorqureshi/web-websocketWeb and bug bounty

web-websocket

⁨Attack WebSocket endpoints — CSWSH (cross-site hijacking), message tampering, and auth gaps. Load on ws:// or wss:// connections, Socket.IO, real-time chat/notifications/trading, or "websocket". Signals: Upgrade: websocket, ws handshake, JSON messages over a socket, token in the handshake.⁩

v2026.10.14-ee0e0c54 installs+4 in 7 days27 StarsMITsynced 22 hours ago

Install

No NotHoly CLI yet? Install it first.

$ curl -fsSL https://notholy.com/install.sh | sh
$ notholy skills install noorqureshi/web-websocket

Writes to ⁦~/.notholy/skills⁩ after checking the signature and the SHA-256.

SignatureSigned, ed25519
xvUbt1Kxue…FCb8GEBg==The CLI checks the SHA-256 and the signature before it writes a file.
Package7302357a…cb6f931f
7302357aff1d…ee6bcb6f931f1 file · ⁦1.3 KB⁩
ScanLowno findings
The scan found nothing to flag in this version.See the full scan
Sourcegithub.com/NoorQureshi/security-skills/tree/main/skills/web/web-websocket@ee0e0c5

When it applies

The app uses WebSockets for realtime features. They're often less-tested than HTTP and skip the authz/validation the REST API has — plus the handshake can be CSRF-able.

Why it works

The WS handshake is an HTTP request that carries cookies; if the server authenticates by cookie alone and doesn't check Origin, any site can open a socket as the victim (Cross-Site WebSocket Hijacking). And per-message authorization is frequently missing — the server trusts the connection.

Method

  1. Intercept & replay: use Burp's WebSocket history to read/modify messages; tamper fields (ids, roles, amounts) and resend — test per-message authz (IDOR/BOLA over the socket).
  2. CSWSH: check if the handshake validates Origin. If not and auth is cookie-based, host a page that opens new WebSocket('wss://target/…') as the victim, then exfiltrate the messages the server sends back → data theft / actions.
  3. Injection: message fields feed backends — test XSS (messages rendered to other users), SQLi/NoSQLi in socket payloads.
  4. Auth gaps: connect without/with a low-priv token; access channels/rooms you shouldn't.

Gotchas

  • CSWSH impact = whatever the socket exposes (private messages, actions) — prove it reads/does something sensitive.
  • Origin check present ≠ safe if it's a weak regex; test bypasses like web-cors.
  • Stored-XSS via chat messages hits other connected users — high impact, easy to miss.

Verify success

Cross-origin socket reading victim data (CSWSH), a tampered message performing an unauthorized action, or an injection firing through a socket message.

References

PortSwigger WebSocket labs; OWASP testing WebSockets (WSTG).

Files in this version

Permissions

PermissionDeclaredFound by the scan
Reads filesNoNo
Writes filesNoNo
Runs shell commandsNoNo
Uses the networkNoNo
Uses connectorsNoNo
Drives a browserNoNo

Scan findings

Reviewed on Nov 13, 2026

The scan found nothing to flag in this version.

A clean scan lowers the risk but does not prove a package is safe. Read what you install.

VersionPublishedCommitSHA-256SignaturePermission change
v2026.10.14-ee0e0c5Nov 13, 2026ee0e0c57302357aSigned–

Ask anything your scope allows.

Create an account, add credits and ask the first question in the chat or the terminal.

  1. 1/3

    Create the account

    Individual or company. You can switch to a company later without losing balance or keys.

    IndividualCompany
  2. 2/3

    Add credits

    By card. Pay per token, no subscription.

    $5.00minimum deposit
  3. 3/3

    Ask

    In the chat, or install the CLI and run notholy login in your terminal.

    $ notholy login