Vai al contenuto
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
meltedinhex/reverse-engineering-custom-c2-protocolsReverse engineering e fuzzing

reverse-engineering-custom-c2-protocols

⁨Reverses proprietary command-and-control protocols: locating send/recv routines,⁩

v1.0.03 installazioni+3 in 7 giorni24 StelleApache-2.0sincronizzato 10 ore fa

Installa

Non hai ancora la CLI di NotHoly? Installala prima.

$ curl -fsSL https://notholy.com/install.sh | sh
$ notholy skills install meltedinhex/reverse-engineering-custom-c2-protocols

Scrive in ⁦~/.notholy/skills⁩ dopo aver controllato la firma e lo SHA-256.

FirmaFirmato, ed25519
69KiTq8UMC…erjx9TDg==La CLI controlla lo SHA-256 e la firma prima di scrivere qualsiasi file.
Pacchetto4c8f5b9e…ff36300e
4c8f5b9e949c…c705ff36300e4 file · ⁦3.1 KB⁩
ScansioneMedio2 segnalazioni
  • Script eseguibile incluso nella skillscripts/analyst.py
  • Link a domini esterni
Vedi la scansione completa
Sorgentegithub.com/meltedinhex/analyst-ai-pack/tree/main/skills/reverse-engineering-custom-c2-protocols@da7600a

Questa voce non è ancora scritta in italiano, quindi è mostrata in un'altra lingua: English.

When to Use

  • A sample uses a non-standard protocol (or a custom layer over HTTP/TCP) and you must decode its traffic.
  • You need to recover message framing, the encryption/encoding scheme, and the command set.
  • You want to build a standalone decoder or emulator to parse captured beacon traffic.

Do not use this for documented protocols handled by existing dissectors — use the protocol analyzer directly instead of reversing from scratch.

Prerequisites

  • A disassembler/debugger and a network capture (PCAP) of the sample's traffic where possible.
  • The crypto/obfuscation skills for recovering keys and encodings.

Workflow

Step 1: Locate the network routines

Find send/recv/WSASend/WinHTTP calls (or the framework wrappers) and the buffers they operate on. These bracket the serialization and crypto.

Step 2: Recover framing

Trace how outbound buffers are built: magic bytes, length prefixes, sequence/ID fields, and type/opcode fields. Document the header layout.

text
[ magic(4) ][ len(4 LE) ][ opcode(1) ][ flags(1) ][ payload(len) ]

Step 3: Recover crypto/encoding

Identify the transform applied before send / after recv (XOR with embedded key, RC4, AES, base64). Recover keys from the binary or from the key-setup routine.

Step 4: Reconstruct the command set

Map opcodes to handlers (shell, download, upload, sleep/jitter, exit) by following the dispatch switch. Build a table of command → behavior.

Step 5: Build a decoder and validate

Implement a parser/decryptor and run it against captured traffic; confirm it yields coherent commands and recovers the beacon's config.

bash
python scripts/analyst.py decode capture.bin --key 0x5a --magic 4d5a4331

Validation

  • The decoder parses every message in a real capture without desync.
  • Decrypted payloads are coherent (printable commands / structured config).
  • The opcode table matches the dispatch logic observed in the binary.

Pitfalls

  • Assuming fixed keys when the protocol negotiates a session key in the first exchange.
  • Missing a length/sequence field and desynchronizing after the first message.
  • Confusing transport (TLS) with the inner custom layer; decode the inner layer.

References

  • See references/api-reference.md for the framing decoder.
  • MITRE ATT&CK T1071 and T1573 (linked in frontmatter).

File di questa versione

Permessi

PermessoDichiaratoTrovato dalla scansione
Legge fileNoNo
Scrive fileNoNo
Esegue comandi shellSìSì
Usa la reteSìSì
Usa i connettoriNoNo
Controlla un browserNoNo

Segnalazioni della scansione

Rivisto il 13 nov 2026

  1. MediaFile · Script eseguibile incluso nella skillscripts/analyst.py
  2. InfoLink · Link a domini esterni

Una scansione pulita abbassa il rischio, ma non prova che il pacchetto sia sicuro. Leggi quello che installi.

VersionePubblicataCommitSHA-256FirmaCambio di permessi
v1.0.013 nov 2026da7600a4c8f5b9eFirmata–

Chiedi tutto quello che il tuo perimetro consente.

Crea un account, aggiungi crediti e fai la prima domanda in chat o nel terminale.

  1. 1/3

    Crea l'account

    Privato o azienda. Puoi passare ad azienda in seguito senza perdere saldo o chiavi.

    PrivatoAzienda
  2. 2/3

    Aggiungi crediti

    Con carta. Paghi a token, senza abbonamento.

    $5.00ricarica minima
  3. 3/3

    Chiedi

    In chat, oppure installa la CLI ed esegui notholy login nel terminale.

    $ notholy login