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
meltedinhex/extracting-cobalt-strike-beacon-configRelatórios e compliance

extracting-cobalt-strike-beacon-config

⁨Extracts and interprets a Cobalt Strike Beacon configuration: decoding the⁩

v1.0.03 instalações+3 em 7 dias24 EstrelasApache-2.0sincronizado há 10 horas

Instalar

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

$ curl -fsSL https://notholy.com/install.sh | sh
$ notholy skills install meltedinhex/extracting-cobalt-strike-beacon-config

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

AssinaturaAssinado, ed25519
7BcmGL7vIi…geRDRdBA==A CLI confere o SHA-256 e a assinatura antes de gravar qualquer arquivo.
Pacote65d2e9f0…b24a71a2
65d2e9f0551c…c170b24a71a24 arquivos · ⁦3.8 KB⁩
VarreduraMédio2 achados
  • Script executável junto com a skillscripts/analyst.py
  • Links para domínios externos
Ver a varredura completa
Fontegithub.com/meltedinhex/analyst-ai-pack/tree/main/skills/extracting-cobalt-strike-beacon-config@da7600a

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

When to Use

  • You have a suspected Cobalt Strike Beacon (PE, DLL, shellcode, or extracted blob) and need its configuration.
  • You want C2 servers, the malleable profile shape, sleep/jitter, watermark, and named pipes.
  • You are building network IOCs and attribution leads from a beacon.

Do not use an extracted config alone for hard attribution — watermarks can be shared or cracked. Treat it as one signal among several.

Prerequisites

  • The beacon payload (or a memory dump containing it) in neutralized form inside the lab.
  • Familiarity with Cobalt Strike's encoded config block (commonly XOR-encoded with 0x2e in older versions, 0x69 in others; varies by version).

Safety & Handling

  • Static extraction only; do not run the beacon.
  • Defang recovered C2 hosts/URIs before sharing.

Workflow

Step 1: Locate the encoded config block

Beacon stores settings as a packed, XOR-encoded table of TLV-like entries. Brute the single-byte XOR key by scanning for the decoded table's known opening bytes (the first setting index/type/length pattern).

Step 2: Decode and parse settings

Once the key is found, walk the entries. Each has an index (setting type), a type (short/int/string), and a length. The script decodes and maps known indices:

bash
python scripts/analyst.py parse beacon.bin

Step 3: Recover key fields

Pull the high-value settings:

text
C2 servers / GET-URI / POST-URI    -> network IOCs
User-Agent                         -> detection signal
Sleep time / jitter                -> beacon cadence
Watermark                          -> license/team grouping lead
Pipe name / process-inject targets -> host IOCs
Spawn-to / DNS settings            -> behavior

Step 4: Interpret the malleable profile

The URIs, headers, and transform settings reveal which malleable C2 profile the operator used (e.g. masquerading as a known web service) — useful for network detection.

Step 5: Build IOCs

Emit network IOCs (hosts, URIs, UA), host IOCs (pipe names), and the watermark for tracking.

Validation

  • The recovered C2 host(s) and URIs are well-formed and consistent with the profile.
  • Sleep/jitter values are plausible and match any observed beaconing intervals.
  • The same config reproduces from an independent extractor or memory copy.

Pitfalls

  • Hardcoding one XOR key — it varies across versions; brute-force per sample.
  • Confusing a watermark match with attribution; cracked/leaked kits share watermarks.
  • Stopping at the first C2 when the config lists multiple/backup servers.

References

  • See references/api-reference.md for the config parser.
  • Cobalt Strike malleable C2 docs and community parser concepts (linked in frontmatter).

Arquivos desta versão

Permissões

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

Achados da varredura

Revisado em 13 de nov. de 2026

  1. MédiaArquivo · Script executável junto com a skillscripts/analyst.py
  2. InfoLink · Links para domínios externos

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
v1.0.013 de nov. de 2026da7600a65d2e9f0Assinada–

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