Explore our new Cybersecurity Terms Glossary, explained by our experts.
Cybersecurity Terms Glossary
Cobalt Strike is a commercial adversary simulation platform whose Beacon implant and customisable C2 profiles made it both the red team standard and a favourite of ransomware crews.

What Is Cobalt Strike?
Cobalt Strike is a commercial platform for adversary simulation, written by Raphael Mudge and first released in 2012, now owned by Fortra. It gives a red team the infrastructure an advanced intrusion set would build for itself: a team server that multiple operators connect to, a post-exploitation implant called Beacon, and a configuration system that lets its network traffic be reshaped to resemble almost anything.
It became the reference tool for one reason above all. Earlier frameworks produced recognisable, noisy traffic. Cobalt Strike let an operator decide what their command and control channel looked like on the wire, which meant a simulation could realistically test whether a defender could spot an intrusion that was not using default settings.
Beacon is the implant. Its defining behaviour is asynchronous operation: rather than holding an open connection, it sleeps for a configured interval, wakes, checks in for tasking, executes, returns results, and sleeps again. Sleep intervals of an hour with random jitter applied are normal in a careful operation, which makes the traffic pattern very different from an interactive session.
Communication options cover HTTP, HTTPS, DNS, and SMB over named pipes. The named pipe mode is important for understanding internal movement: a Beacon on a host with no internet access connects through another Beacon that does, so a server deep in a segmented network is controlled entirely over internal SMB traffic with a single egress point.
Malleable C2 profiles define the request and response formats, headers, URIs, user agent strings, and the encoding used to hide tasking inside apparently normal traffic. Published profiles imitate specific legitimate services, and operators write their own. This is the feature that makes network signature detection a losing game played on its own.
Post-exploitation runs largely in memory. Beacon object files execute compiled C in the Beacon process without spawning anything, and the execute-assembly command runs .NET tooling in memory. Together these avoid writing tools to disk, which is why detection has had to move to behavioural indicators and memory inspection.
A legitimate Cobalt Strike licence costs several thousand pounds per user per year and is sold subject to vetting. Cracked copies of older versions have circulated freely for years, and the result is that a tool designed for authorised simulation became the standard intrusion toolkit for criminal groups. Conti, Ryuk, and a long list of ransomware affiliates used it as their primary post-exploitation platform, and by 2021 security vendors were reporting Cobalt Strike Beacon as one of the most frequently observed implants in real intrusions.
In April 2023, Microsoft’s Digital Crimes Unit, Fortra, and Health-ISAC obtained a court order in the Eastern District of New York authorising the seizure of infrastructure hosting cracked copies, as part of a coordinated effort to reduce their availability. Fortra has also tightened licensing and watermarking. Cracked builds remain in circulation, but the tool’s dominance has been eroded as much by defenders learning to detect it as by enforcement, which is why newer frameworks such as Havoc and Sliver have gained ground.
Mature detection stacks catch default Cobalt Strike comfortably and skilled operators with difficulty. The approaches that work:
rundll32.exe with no arguments, Office applications spawning script hosts, and unusual processes making outbound connections.Mapping these to MITRE ATT&CK and testing them deliberately in a purple team session is far more productive than buying another feed of Cobalt Strike indicators, which age in days.
Possession and use of Cobalt Strike against systems you are not authorised to test engages the Computer Misuse Act 1990, and section 3A of that Act covers making or supplying articles for use in computer misuse offences. Authorised engagements require a written scope, named operators, agreed infrastructure, and a record of activity that lets the client distinguish simulation from a genuine intrusion. Deconfliction contacts should be agreed before the first implant is deployed.
At Privia Security, our Red Team Services run adversary simulation with recorded tradecraft and an activity timeline your defenders can replay against their own telemetry.
Because cracked copies of older versions circulate freely and the tool is extremely capable. It provides stable implants, flexible traffic shaping, in-memory execution, and multi-operator infrastructure that would take a criminal group months to build. Microsoft, Fortra, and Health-ISAC obtained a court order in April 2023 to seize infrastructure hosting cracked copies, but availability has not been eliminated.
Default configurations, generally yes. Modern endpoint detection products identify Beacon in memory, flag its injection behaviour, and recognise common named pipe patterns. Operators using custom malleable profiles, sleep obfuscation, and custom loaders defeat signature matching, which is why detection has to rest on behaviour: unbacked executable memory, remote thread creation, and unusual process lineage.
A configuration file defining exactly how Beacon’s network traffic looks: the URIs requested, the headers sent, the user agent string, where tasking is hidden in the request, and how responses are encoded. It lets an operator make command and control traffic resemble a legitimate service. It is also why network signatures alone do not detect a competent operator.
Run a purple team exercise rather than buying indicator feeds, which age within days. Have the red team execute specific techniques openly, map each to MITRE ATT&CK, and check what the endpoint and network telemetry recorded, what alerted, and what was missed. Write detections for the behaviours that went unseen, then repeat the technique to confirm the rule fires.
You May Be Interested In These
We use a few cookies that are needed to make this website work, and they are always on. We would also like to set analytics cookies, to see which pages are useful; functional cookies, so that our live chat works; and advertising cookies, to measure our campaigns. We will not set any of those until you say yes, and you can change your mind at any time from the Cookie Settings link in the footer.
Choose the cookies you are happy for us to use. Strictly necessary cookies are always on; everything else is off until you turn it on.
These cookies keep the website working: they hold your security checks, your form submissions and the choice you make here. The site cannot run without them, so they are always on.
These let our live chat open and remember your conversation, and let the newsletter sign-up work. Switch them off and the chat window will not appear.
These tell us which pages are read and how people find us, so that we can improve the site. The reports are about groups of visitors, never about you personally.
These let us measure our advertising and show you our adverts on other websites, such as LinkedIn, Google and Meta. Switch them off and you will still see adverts, but they will be less relevant.