[Originally posted on ImplicitDeny] - This write up is for Empire 1.5, but the same concepts and commands are the same. In Part One we went over the reasons for having a resilient C2 infrastructure, and what it should look like. In summary, we want to have two or more internet accessible servers to host the different …
Continue reading Rome Didn’t Fall in a Day: Building A Resilient Empire C2, Part Two
Now that the Empire project has released the Dropbox Listener module to public with v2, let's get it setup. For those organizations that are not blocking Dropbox, this is an excellent and highly reliable C2 channel. It can probably go without saying that one of the coolest things about this module is that the attacker network is …
[Originally posted at ImplicitDeny] In this two-part series, we will walk through building an infrastructure to host your command and control (C2). At the end of this series, you should have at least two servers ready for your engagement. One server will be a simple web server to host your stagers, and the other will …
Continue reading Rome Didn’t Fall in a Day: Building A Resilient Empire C2, Part One
bluescreenofjeff is doing amazing stuff with automating tasks in Cobalt Strike (CS), and I must admit quite a bit of CS jealousy from the first time I was introduced to it. Aggressor scripts are the shiz-nit. We're all doing similar tasks in this offensive security field, and automation is a big part of it. Doing something …
bneg 