competition-pcap-protocol

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Chinese

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.

仅可在

$ctf-sandbox-orchestrator

已激活并确定沙箱假设、节点归属和证据优先级后，作为下游专属技能使用本技能。如果还未满足上述前置条件，请先返回

$ctf-sandbox-orchestrator

。

当决定性证据存在于数据包顺序、协议帧结构或流重组结果中，而非单一IOC或主机日志时，使用本技能。

除非用户明确要求英文，否则请用简体中文回复。

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

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.

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.

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.

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
```
.

加载
```
references/pcap-protocol.md
```
查看会话检查清单、解码检查清单和证据打包规范。
如果难点是WebSocket或SSE握手、订阅流程、实时帧或帧驱动状态，请优先使用
```
$competition-websocket-runtime
```
。
如果难点是自定义握手、帧结构、校验和、序列依赖或确定性重放测试工具，请优先使用
```
$competition-custom-protocol-replay
```
。

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