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-custom-protocol-replayAnálise de malware e ransomware

competition-custom-protocol-replay

⁨Internal downstream skill for ctf-sandbox-orchestrator. CTF-sandbox workflow for custom binary or text protocol recovery, handshake reconstruction, framing, sequence control, checksums, stateful replay, and accepted-session reproduction. Use when the user asks to decode an unknown protocol, recover ⁩

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-custom-protocol-replay

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

AssinaturaAssinado, ed25519
BuhSC72sBO…yY3liOBg==A CLI confere o SHA-256 e a assinatura antes de gravar qualquer arquivo.
Pacoteb730ae8e…bd5b65b1
b730ae8e2f99…5268bd5b65b13 arquivos · ⁦2.0 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-custom-protocol-replay@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 hard part is not merely naming the protocol, but reproducing the exact message order and state needed for acceptance.

Reply in Simplified Chinese unless the user explicitly requests English.

Quick Start

  1. Identify client and server roles, session boundaries, and reset conditions before decoding field semantics.
  2. Recover framing, lengths, delimiters, sequence numbers, checksums, nonces, and state transitions before broad replay attempts.
  3. Keep one canonical transcript of a successful exchange.
  4. Change one field or one message at a time while replaying.
  5. Reproduce the smallest accepted conversation that proves the decisive branch.

Workflow

1. Map The Session State Machine

  • Identify handshake, negotiation, authentication, keepalive, command, and teardown phases.
  • Record which fields are static, which are derived, and which depend on prior messages.
  • Keep message order, direction, and timing tied to the same session identity.

2. Recover Framing And Integrity

  • Reconstruct lengths, delimiters, type bytes, checksums, MACs, counters, compression, or encryption boundaries.
  • Distinguish transport framing from application-level framing.
  • Note exactly where server acceptance changes when one field or step is mutated.

3. Build The Minimal Replay Harness

  • Reduce the path to the smallest transcript that reaches the accepted state, parser branch, command effect, or artifact.
  • Preserve both the original captured sequence and the replayed minimal sequence.
  • If the problem is mainly generic PCAP or stream decoding with no stateful replay requirement, switch back to the broader PCAP skill.

Read This Reference

  • Load references/custom-protocol-replay.md for the state-machine checklist, transcript checklist, and evidence packaging.

What To Preserve

  • Canonical transcript, message types, field boundaries, checksums, counters, and session identifiers
  • Original capture slices and the replay harness inputs that produce acceptance
  • The exact mutation that flips the protocol from rejected to accepted, or vice versa

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 2026cab634bb730ae8eAssinada–

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