Anthropic Cybersecurity Skills is a library of structured cybersecurity procedures for AI agents, covering security domains and mappings to established security frameworks. It is for authorized security analysis, penetration testing, incident response, research, defense, and education across compatible AI platforms. The catalogue entries package parts of this library as agent skills, instructions, or a plugin.
Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add mukul975/Anthropic-Cybersecurity-Skills --skill analyzing-cobalt-strike-beacon-configurationgit clone --depth 1 https://github.com/mukul975/Anthropic-Cybersecurity-SkillsWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/mukul975/anthropic-cybersecurity-skills/analyzing-cobalt-strike-beacon-configuration)<a href="https://agentmods.dev/skills/mukul975/anthropic-cybersecurity-skills/analyzing-cobalt-strike-beacon-configuration"><img src="https://agentmods.dev/badge/skills/mukul975/anthropic-cybersecurity-skills/analyzing-cobalt-strike-beacon-configuration/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/mukul975/anthropic-cybersecurity-skills/analyzing-cobalt-strike-beacon-configuration"><img src="https://agentmods.dev/badge/skills/mukul975/anthropic-cybersecurity-skills/analyzing-cobalt-strike-beacon-configuration.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket pass
- Snyk fail
- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to critical
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- critical YARA Match · line 47 YARA rule matched a known malware signature (reverse shell, backdoor, ransomware, C2 framework, or info stealer).Fix: Remove the malware payload or compromised file entirely. Investigate how it entered the skill and audit all other artifacts for additional indicators of compromise.
What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00042 | $0.03334 |
| Opus 5 | $0.00021 | $0.01667 |
| Sonnet 5 | $0.00008 | $0.00667 |
| Haiku 4.5 | $0.00004 | $0.00333 |
Grade A, and why
analyzing-cobalt-strike-beacon-configuration scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 13d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
Copies of this mod
7 near-identical copies found in the catalogue:
- analyzing-cobalt-strike-beacon-configuration — 100% identical, 0 lines differ
- analyzing-cobalt-strike-beacon-configuration — 98% identical, 11 lines differ
- analyzing-cobalt-strike-beacon-configuration — 98% identical, 26 lines differ
- analyzing-cobalt-strike-beacon-configuration — 98% identical, 26 lines differ
- analyzing-cobalt-strike-beacon-configuration — 98% identical, 11 lines differ
- analyzing-cobalt-strike-beacon-configuration — 98% identical, 26 lines differ
- analyzing-cobalt-strike-beacon-configuration — 91% identical, 36 lines differ
How it starts
The opening of the file, as written. The whole thing — 389 lines — stays where its author put it; the contents beside it link to each section on GitHub.
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 - SentinelOne CobaltStrikeParser (
parse_beacon_config.py) - Hex editor (010 Editor, HxD) for manual inspection
- Understanding of PE file format and XOR encoding
- Memory dump acquisition tools (Volatility3, WinDbg)
- Network analysis tools (Wireshark) for C2 traffic correlation
Key Concepts
Beacon Configuration Structure
Cobalt Strike beacons store their configuration as a blob of TLV (Type-Length-Value) entries within the .data section of the PE. Stageless beacons XOR the entire beacon code with a 4-byte key. The configuration blob itself uses a single-byte XOR key. Each TLV entry contains a 2-byte type identifier (e.g., 0x0001 for BeaconType, 0x0008 for C2Server), a 2-byte length, and variable-length data.
Malleable C2 Profiles
The beacon configuration encodes the malleable C2 profile that dictates HTTP request/response transformations, including URI paths, headers, metadata encoding (Base64, NetBIOS), and data transforms. Analyzing these settings reveals how the beacon disguises its traffic to blend with legitimate web traffic.
What ships with it
7 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 13d ago First seen · 389 lines · 42 tokens per session scan A ce44cb3f75aa
analyzing-cobalt-strike-beacon-configuration is a skill published in the GitHub repository mukul975/Anthropic-Cybersecurity-Skills (32,631 stars, last pushed 12d ago), licensed Apache-2.0. It adds 42 tokens to every session and 3,334 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
analyzing-cobalt-strike-beacon-configuration
Use when extract and analyze Cobalt Strike beacon configuration from PE files and memory dumps to identify C2 infrastructure, malleable profiles, and operator tradecraft. Use when working with analyzing cobalt strike beacon configuration.
analyzing-cobalt-strike-beacon-configuration
Extract and analyze Cobalt Strike beacon configuration from PE files and memory dumps to identify C2 infrastructure, malleable profiles, and operator tradecraft.
analyzing-cobalt-strike-beacon-configuration
A guide to extracting and examining Cobalt Strike Beacon settings from Windows executable files or memory dumps. Cobalt Strike is a security testing tool often misused by attackers, and Beacon is its remotely controlled payload.
analyzing-cobalt-strike-beacon-configuration
Extract and analyze Cobalt Strike beacon configuration from PE files and memory dumps to identify C2 infrastructure, malleable profiles, and operator tradecraft.
analyzing-cobalt-strike-beacon-configuration
Extract and analyze Cobalt Strike beacon configuration from PE files and memory dumps to identify C2 infrastructure, malleable profiles, and operator tradecraft.
analyzing-cobalt-strike-beacon-configuration
Extract and analyze Cobalt Strike beacon configuration from PE files and memory dumps to identify C2 infrastructure, malleable profiles, and operator tradecraft.