extracting-cobalt-strike-beacon-config
Extracts and interprets a Cobalt Strike Beacon configuration: decoding the
v1.0.03 instalaciones+3 en 7 días24 EstrellasApache-2.0sincronizado hace 10 horas
Instalar
¿Aún no tienes la CLI de NotHoly? Instálala primero.
$ curl -fsSL https://notholy.com/install.sh | sh$ notholy skills install meltedinhex/extracting-cobalt-strike-beacon-configEscribe en ~/.notholy/skills después de comprobar la firma y el SHA-256.
FirmaFirmado, ed25519
Paquete65d2e9f0…b24a71a2
65d2e9f0551c…c170b24a71a24 archivos · 3.8 KBEscaneoMedio2 hallazgos
- Script ejecutable incluido con la skillscripts/analyst.py
- Enlaces a dominios externos
Fuentegithub.com/meltedinhex/analyst-ai-pack/tree/main/skills/extracting-cobalt-strike-beacon-config@da7600a
Esta entrada todavía no está escrita en tu idioma, así que aparece en English.
En esta página
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:
python scripts/analyst.py parse beacon.binStep 3: Recover key fields
Pull the high-value settings:
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 -> behaviorStep 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.mdfor the config parser. - Cobalt Strike malleable C2 docs and community parser concepts (linked in frontmatter).
Archivos de esta versión
references/11.5 KB
- api-reference.md1.5 KB
scripts/13.2 KB
- analyst.py3.2 KB
- LICENSE340 B
- SKILL.md3.6 KB
Permisos
| Permiso | Declarado | Hallado en el escaneo |
|---|---|---|
| Lee archivos | No | No |
| Escribe archivos | No | No |
| Ejecuta comandos de shell | Sí | Sí |
| Usa la red | Sí | Sí |
| Usa conectores | No | No |
| Controla un navegador | No | No |
Hallazgos del escaneo
Revisado el 13 nov 2026
- MediaArchivo · Script ejecutable incluido con la skillscripts/analyst.py
- InfoEnlace · Enlaces a dominios externos
Un escaneo limpio baja el riesgo, pero no prueba que el paquete sea seguro. Lee lo que instalas.
| Versión | Publicada | Commit | SHA-256 | Firma | Cambio de permisos |
|---|---|---|---|---|---|
| v1.0.0 | 13 nov 2026 | da7600a | 65d2e9f0 | Firmada | – |
Más de meltedinhex
Todo de este publicador- writing-yara-rules-from-reversed-codemeltedinhex/writing-yara-rules-from-reversed-code4
- validating-detections-with-atomic-testsmeltedinhex/validating-detections-with-atomic-tests4
- writing-suricata-and-snort-rulesmeltedinhex/writing-suricata-and-snort-rules3
- writing-sigma-detection-rulesmeltedinhex/writing-sigma-detection-rules3
Más en Informes y cumplimiento
Ver la categoría- skillduty1g/skill5
- rea-ci-tests-auditmorluto/rea-ci-tests-audit4
- tracking-threat-actor-infrastructuremukul975/tracking-threat-actor-infrastructure4
- performing-authenticated-scan-with-openvasmukul975/performing-authenticated-scan-with-openvas4
- slicing-code-contexttrailofbits/slicing-code-context4
- 1337aeondave/13374
Pregunta todo lo que tu alcance permite.
Crea la cuenta, añade créditos y haz la primera pregunta en el chat o en la terminal.
- 1/3
Crea la cuenta
Individual o empresa. Puedes pasar a empresa después sin perder saldo ni claves.
IndividualEmpresa - 2/3
Añade créditos
Con tarjeta. Pagas por token, sin suscripción.
$5.00recarga mínima - 3/3
Pregunta
En el chat, o instala el CLI y ejecuta notholy login en tu terminal.
$ notholy login