analyzing-cobalt-strike-beacon-configuration SKILL.md skillA
analyzing-cobalt-strike-beacon-configuration from 26zl/cybersec-toolkit is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add 26zl/cybersec-toolkit/analyzing-cobalt-strike-beacon-configuration@v1.0Pins v1.0 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- 26zl/cybersec-toolkit
- Path
.claude/skills/analyzing-cobalt-strike-beacon-configuration/SKILL.md- Versions recorded
- 1
- Latest version
- v1.0, committed Apr 30, 2026
- Size
- 12,997 bytes
- Repository stars
- 87
- License
- MIT
Extract and analyze Cobalt Strike beacon configuration from PE files and memory dumps to identify C2 infrastructure,.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Analyzing Cobalt Strike Beacon Configuration ## Overview Cobalt Strike is a commercial adversary simulation tool widely abused by threat actors for post-exploitation operations. Beacon payloads contain embedded configuration data that reveals C2 server addresses, communication protocols, sleep intervals, jitter values, malleable C2 profile settings, watermark identifiers, and encryption keys. Extracting this configuration from PE files, shellcode, or memory dumps is critical for incident responders to map attacker infrastructure and attribute campaigns. The beacon configuration is XOR-encoded using a single byte (0x69 for version 3, 0x2e for version 4) and stored in a Type-Length-Value (TLV) format within the .data section. ## When to Use - When investigating security incidents that require analyzing cobalt strike beacon configuration - When building detection rules or threat hunting queries for this domain - When SOC analysts need structured procedures for this analysis type - When validating security monitoring coverage for related attack techniques ## Prerequisites - Python 3.9+ with `dissect.cobaltstrike`, `pefile`, `yara-python` …
Read the whole file at its exact version.
How to install
mdr add 26zl/cybersec-toolkit/analyzing-cobalt-strike-beacon-configuration@sha256:85e12a0f8dcfc8deThe line at the top of this page pins the label v1.0, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_f2wsn4xqctjb2sgv)
0 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Apr 30, 2026.
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (12997 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
26zl/cybersec-toolkit · 87 stars · license MIT · pushed 2026-11-01 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_f2wsn4xqctjb2sgv GET https://markdownregistry.com/api/v1/resolve?ref=26zl/cybersec-toolkit/analyzing-cobalt-strike-beacon-configuration GET https://markdownregistry.com/api/v1/blob/85e12a0f8dcfc8de9c6b0efc0f015254378b76f368533cc6df5b084c8885b78e
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.
More from 26zl/cybersec-toolkit
Every file in 26zl/cybersec-toolkit