Pular para o conteúdo
Novo

DeepSeek V4.1 Flash grátis por 7 dias: 10M tokens por dia após recarga de $10 ou mais. Até 30/11.

Como funciona
zhaoxuya520/competition-pcap-protocolRede, wireless e 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 instalações+3 em 7 dias44,8 mil EstrelasMITsincronizado há 2 horas

Instalar

Ainda não tem a CLI da NotHoly? Instale primeiro.

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

Grava em ⁦~/.notholy/skills⁩ depois de conferir a assinatura e o SHA-256.

AssinaturaAssinado, ed25519
P9YsmlVCzg…6Ii1rYCQ==A CLI confere o SHA-256 e a assinatura antes de gravar qualquer arquivo.
Pacote8f254b64…4730d02b
8f254b64e20b…fa434730d02b3 arquivos · ⁦2.2 KB⁩
VarreduraBaixonenhum achado
A varredura não encontrou nada para apontar nesta versão.Ver a varredura completa
Fontegithub.com/zhaoxuya520/reverse-skill/tree/main/CTF-Sandbox-Orchestrator/competition-pcap-protocol@cab634b

Este item ainda não foi escrito no seu idioma, então aparece em English.

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

Arquivos desta versão

Permissões

PermissãoDeclaradaEncontrada na varredura
Lê arquivosNãoNão
Grava arquivosNãoNão
Roda comandos no shellNãoNão
Usa a redeNãoNão
Usa conectoresNãoNão
Controla um navegadorNãoNão

Achados da varredura

Revisado em 13 de nov. de 2026

A varredura não encontrou nada para apontar nesta versão.

Uma varredura limpa reduz o risco, mas não prova que o pacote é seguro. Leia o que você instala.

VersãoPublicada emCommitSHA-256AssinaturaMudança de permissão
v2026.9.22-cab634b13 de nov. de 2026cab634b8f254b64Assinada–

Pergunte tudo o que o seu escopo permite.

Crie a conta, adicione créditos e faça a primeira pergunta no chat ou no terminal.

  1. 1/3

    Crie a conta

    Individual ou empresa. Dá para virar empresa depois sem perder saldo nem chaves.

    Pessoa físicaEmpresa
  2. 2/3

    Adicione créditos

    No cartão. Você paga por token, sem assinatura.

    $5.00recarga mínima
  3. 3/3

    Pergunte

    No chat, ou instale o CLI e rode notholy login no terminal.

    $ notholy login