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
zhaoxuya520/competition-websocket-runtimeMalware and ransomware analysis

competition-websocket-runtime

⁨Internal downstream skill for ctf-sandbox-orchestrator. CTF-sandbox workflow for WebSocket and SSE handshakes, auth material, subscription state, realtime message schemas, reconnect behavior, and frame-driven runtime effects. Use when the user asks to inspect a WebSocket or SSE handshake, decode fra⁩

v2026.9.22-cab634b2 installs+2 in 7 days44.8K StarsMITsynced 2 hours ago

Install

No NotHoly CLI yet? Install it first.

$ curl -fsSL https://notholy.com/install.sh | sh
$ notholy skills install zhaoxuya520/competition-websocket-runtime

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

SignatureSigned, ed25519
h76Y9aMYZp…NOdDCFAA==The CLI checks the SHA-256 and the signature before it writes a file.
Package5d5676a9…0d661bfe
5d5676a932fe…59ab0d661bfe3 files · ⁦2.0 KB⁩
ScanLowno findings
The scan found nothing to flag in this version.See the full scan
Sourcegithub.com/zhaoxuya520/reverse-skill/tree/main/CTF-Sandbox-Orchestrator/competition-websocket-runtime@cab634b

Use this skill only as a downstream specialization after $ctf-sandbox-orchestrator is already active and has established sandbox assumptions, node ownership, and evidence priorities. If that has not happened yet, return to $ctf-sandbox-orchestrator first.

Use this skill when the decisive behavior is carried by realtime handshake and frame flow rather than one-shot HTTP alone.

Reply in Simplified Chinese unless the user explicitly requests English.

Quick Start

  1. Map the handshake first: origin, path, headers, cookies, query, auth token, and upgrade response.
  2. Separate connection setup, subscription messages, keepalives, server pushes, and reconnect logic.
  3. Record message schema, topic or channel identity, and state side effects in one chain.
  4. Tie frames to rendered, stored, or backend-visible effects.
  5. Reproduce the smallest handshake-plus-frame sequence that reaches the decisive state change.

Workflow

1. Map The Realtime Handshake

  • Record the initial HTTP or SSE request, upgrade headers, cookies, tokens, query params, origin checks, and negotiated protocol.
  • Note whether auth material is carried by headers, cookies, query strings, or initial application frames.
  • Keep route, subscription endpoint, and session identity tied together.

2. Decode Message Flow

  • Separate subscribe, unsubscribe, ack, heartbeat, server push, reconnect, and terminal frames.
  • Recover message types, channel IDs, schema fields, and sequencing that matter to behavior.
  • Distinguish transport keepalive from application-level business messages.

3. Reduce To The Decisive Realtime Path

  • Compress the result to the smallest sequence: handshake -> auth or subscribe frame -> pushed or accepted frame -> resulting state change.
  • Keep canonical frame order and any replayed minimal order side by side.
  • If the hard part is generic protocol reassembly without runtime UI or app-state linkage, switch back to the tighter protocol skill.

Read This Reference

  • Load references/websocket-runtime.md for the handshake checklist, frame checklist, and evidence packaging.

What To Preserve

  • Handshake headers, cookies, query params, auth material, negotiated subprotocol, and channel IDs
  • Frame schemas, subscription messages, server pushes, reconnect flow, and resulting state changes
  • The smallest replayable realtime sequence that proves the decisive branch

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.9.22-cab634bNov 13, 2026cab634b5d5676a9Signed–

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