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-pcap-protocolNetwork, wireless and telecom

competition-pcap-protocol

⁨Internal downstream skill for ctf-sandbox-orchestrator. CTF-sandbox workflow for packet capture analysis, session reconstruction, application-protocol decoding, stream reassembly, beacon timing, and packet-to-process correlation. Use when the user asks to analyze a PCAP, rebuild TCP or UDP sessions,⁩

v2026.9.22-cab634b3 installs+3 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-pcap-protocol

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

SignatureSigned, ed25519
P9YsmlVCzg…6Ii1rYCQ==The CLI checks the SHA-256 and the signature before it writes a file.
Package8f254b64…4730d02b
8f254b64e20b…fa434730d02b3 files · ⁦2.2 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-pcap-protocol@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 evidence sits inside packet order, protocol framing, or stream reconstruction rather than a single IOC or host log.

Reply in Simplified Chinese unless the user explicitly requests English.

Quick Start

  1. Establish the capture boundaries first: hosts, time span, interfaces, missing packets, retransmits, and stream count.
  2. Group traffic into sessions before decoding payload semantics.
  3. Record protocol framing, sequence, timing, and transferred artifacts together instead of as isolated packets.
  4. Correlate packet evidence with host, malware, or app behavior only after the session is reconstructed.
  5. Reproduce the smallest decoded stream or transferred artifact that proves the challenge path.

Workflow

1. Build The Session Map

  • Identify endpoints, protocols, ports, TLS handshakes, DNS lookups, websocket upgrades, and long-lived streams.
  • Note missing capture coverage, asymmetric routing, packet loss, or reassembly issues before drawing conclusions.
  • Separate control channels, bulk transfers, keepalives, and noise.

2. Decode The Protocol Boundary

  • Reassemble TCP streams or UDP conversations before interpreting fields.
  • Recover framing, message order, custom headers, binary fields, compression, encryption boundaries, and object transfers.
  • Keep payload direction, timing, and session state aligned with each decoded message.

3. Tie Packets To Behavior

  • Show which packet sequence maps to which host event, malware branch, login flow, upload, exfiltration step, or command channel.
  • Distinguish protocol recognition from artifact recovery: naming HTTP, DNS, or a custom C2 is not enough without decoded content or proven downstream effect.
  • If the task becomes mostly a host timeline problem after decode, switch to the tighter forensic timeline skill.

Read This Reference

  • Load references/pcap-protocol.md for the session checklist, decode checklist, and evidence packaging.
  • If the hard part is a WebSocket or SSE handshake, subscription flow, realtime frames, or frame-driven state, prefer $competition-websocket-runtime.
  • If the hard part is a custom handshake, framing, checksum, sequence dependency, or deterministic replay harness, prefer $competition-custom-protocol-replay.

What To Preserve

  • Stream IDs, endpoint pairs, packet ranges, timestamps, protocol framing, and object boundaries
  • Decoded requests, responses, commands, transferred files, and the session that carried them
  • The exact packet sequence or reconstructed stream that proves the challenge behavior

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, 2026cab634b8f254b64Signed–

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