Integrating C3 With Cobalt Strike via ExternalC2 And Studying Their Behavior

Cobalt Strike is the industry standard for C2 projects. It provides a post-exploitation agent and channels to emulate long-term embedded actors in networks. Cobalt Strike can use very good surreptitiously channels via many different techniques.

One interesting feature Cobalt Strike provides is called the ExternalC2 link, which allows attackers to lengthen the default HTTP(S)/DNS/SMB C2 communication channels contributed by using additional nodes in the middle of the channels. In this post, I will discuss the use of this feature after Integrating it with the new C3 project by FSecureLabs. Then review the imperceptibility, robustness, throughput, detection, and prevention of this implementation.


C3 stands for custom command control; this tool is made FSecureLABS and was released publicly on September 2nd this year. This is a very new project, and the idea of it is quite fascinating, in a recent blog post made by FSecureLabs about C3 they state, “It is a tool that allows Red Teams to rapidly develop and utilize esoteric command and control channels (C2). It’s a framework that extends another red team tooling (FSecureLabs, 2019).”


Windows has become much more secure over the years with Windows Defenders and the Anti Malware Scan Interface becoming something attackers can no longer ignore. As blue teamers evolve their craft so must red teamers, with the advent of C3, this makes our C2 traffic essentially blend in network traffic as to not raise suspicions. Furthermore, showing that we can integrate C3 with industry-standard red team adversary simulation software such as Cobalt Strike, this means that other red teamers can adapt these tools and techniques into their toolkit. Overall, this is important because this allows red teamers to become less suspicious and appear like genuine traffic; this helps red teamers less likely to get detected.




Setting up Cobalt Strike Team server

Setting up CS Team server

$ ./teamserver <IP Addresss> <Team Password>


Cobalt Strike Client Test

$ ./CobaltStrike

Enter the team server IP Address, Port, username, and password. CS1

Setting up C3

First, there are a couple of dependencies C3 needs to be installed.

  • Dotnet corse 2.2,
  • Visual C++ Redistributable for Visual Studio 2015,
  • C3,

Start WebController

Screenshot of C3 WebController running command

As a result, the WebController will start at port 8080, and you can go to http://- C3 IP -/. In my case, it is

Screenshot of the WebController from the browser.

Configure a C3 gateway

Configure a gateway to start using C3 and download the zip file.

Screenshot of the our gateway configuration.

Unzip the file and run GatewayConsoleExe.exe so it connected to the Gateway.


Wait for a minute until it connects. After almost a minute, Refresh the Gateway page. It will show up a page as shown below.

Screenshot of the main page.

Linking CS with C3

Now to link Gateway to Team Server we need to follow the next steps

Configure the CS side

Create a file with this content

externalc2_start("", 51002);

Load it into Cobalt Strike


It should be loaded and it should show the script as shown below.


Configure the C3 side

Connect the C3 Gateway to Cobalt Strike.

Connecting the C3 Gateway to Cobalt Strike.

For the channel we use Slack, we created a Slack App in a Slack Workspace. The Bot Permissions we used are shown below.

Bot Permissions.

In the C3 Dashboard, click the Gateway > Command Center > AddChannelSlack and paste Slack token.

As a result, the topology will change as shown

Screenshot of the main dashboard with the new Slack Channel connected.

Creating a node relay setup

Next, we need to create a Node Relay for this C2 channel that we will run on a compromised host.

Click on the Slack Channel Interface > Options > New Relay. Then run it on the compromised host.

As a result, the topology will change as shown.

Screenshot of the main dashboard with the new relay connected.

Send Beacons to Cobalt Strike

To deploy a CS Beacon, click Command Center > AddPeripheralBeacon > Send Command. Then after waiting for less than a minute. The C3 Dashboard will show a new interface for the new beacon sent.


Cobalt Strike Dashboard will also have will show a new session.



Network behavior

I captured the traffic on the blue side and noticed that all the traffic is normal since it’s communicating with Slack’s server, and I like that it’s using HTTPS. But I can say that it’s too noisy. a whoami command generates +30 packets, which is a little bit suspicious, especially when I dump hashs; It generates uncountable packets. In a future post, I will try to analyze the captures and identifies the unusual characteristics.

Slack channel behavior

I notice when the C3 sends and receives data. It encodes the messages (maybe enctype, not sure, but the messages end with == so I guess it’s just encoding) from both ends. And when it finishes using the sent messages, it deletes the messages, which is something I liked.


The main problem in this implementation is the Relay binary/DLL. The implant needs to be loaded and running on the blue team side. Which is by using the default binary or Dll, just running the exe file is easily detectable. And the DLL implant is a better option but still not persistent after rebooting the system; thus, more persistence techniques need to be integrated with the implant to make sure it’s working all the time, otherwise, we lose cobalt strike beacons.


C3 is an amazing project. Very helpful and adds more implants in the blue teamers’ servers that behave differently, thus more ways into their systems, thus, more persistence. I think in future Red Team competitions, I would use it as a kind of last resort implants. Finally, special thanks to @notoriousRebel1 for helping me making this work.