Leaving your c2 to use SSH, MSF, nmap - HUGE pain.
Why not just use them from the browser!
Since realm's network proxy is all server side we were able to build other things like SSH into the backend and in go connect the sockets.
New file hosting feature! ๐
Host files and share them for a duration or with a specific number of downloads.
Or use them directly in the imix agent.
### Top-Line Findings
1. **The C2 ecosystem is far less diverse than it appears.** While there are 30+ "different" frameworks, the underlying technique implementations converge on a small number of canonical code patterns, many traceable to specific open-source authors or blog posts.
2. **Three source projects account for the majority of reused code:**
- **TrustedSec's COFFLoader** โ the ancestor of nearly every open-source BOF loader
- **PowerSploit** (by @harmj0y, @mattifestation, @obscuresec) โ Get-Keystrokes, Invoke-Mimikatz, PowerView, and persistence modules are shipped verbatim by Empire, PoshC2, PowerHub, Amnesiac, and Shad0w
- **Kevin Robertson's Invoke-WMIExec/Invoke-SMBExec** โ the dominant PowerShell implementations for WMI and SMB lateral movement, bundled by Empire, PoshC2, PowerHub, and SilentTrinity
3. **A single detection rule can catch multiple frameworks.** Because many C2s share identical implementation code:
- One detection for the PowerSploit `Get-Keystrokes` GetAsyncKeyState polling loop catches Empire, PoshC2, and any framework that bundles PowerSploit
- One detection for the TrustedSec COFFLoader relocation pattern catches Apollo, Loki, Sliver (extension), and derivatives
- One detection for the .NET `ManagementScope` WMI pattern catches Apollo, Covenant, NimboC2, SilentTrinity, and DeimoC2
4. **Genuinely novel frameworks are rare.** Of the 30 analyzed:
- **4 frameworks** (Sliver, Havoc, Realm, TripleCross) demonstrate significant code originality
- **6 frameworks** show moderate originality (Wyrm, AdaptixC2, Emp3r0r, Merlin, NimPlant, GC2)
- **20 frameworks** rely heavily on shared code from the three source projects above, or implement techniques using the same well-known recipes
5. **HTTP C2 communications show the most behavioral convergence.** Three jitter formula families, shared User-Agent strings (the IE11 UA appears in Empire, Nuages, and Covenant), and common URL path patterns create fingerprinting opportunities.
### Top-Line Findings
1. **The C2 ecosystem is far less diverse than it appears.** While there are 30+ "different" frameworks, the underlying technique implementations converge on a small number of canonical code patterns, many traceable to specific open-source authors or blog posts.
2. **Three source projects account for the majority of reused code:**
- **TrustedSec's COFFLoader** โ the ancestor of nearly every open-source BOF loader
- **PowerSploit** (by @harmj0y, @mattifestation, @obscuresec) โ Get-Keystrokes, Invoke-Mimikatz, PowerView, and persistence modules are shipped verbatim by Empire, PoshC2, PowerHub, Amnesiac, and Shad0w
- **Kevin Robertson's Invoke-WMIExec/Invoke-SMBExec** โ the dominant PowerShell implementations for WMI and SMB lateral movement, bundled by Empire, PoshC2, PowerHub, and SilentTrinity
3. **A single detection rule can catch multiple frameworks.** Because many C2s share identical implementation code:
- One detection for the PowerSploit `Get-Keystrokes` GetAsyncKeyState polling loop catches Empire, PoshC2, and any framework that bundles PowerSploit
- One detection for the TrustedSec COFFLoader relocation pattern catches Apollo, Loki, Sliver (extension), and derivatives
- One detection for the .NET `ManagementScope` WMI pattern catches Apollo, Covenant, NimboC2, SilentTrinity, and DeimoC2
4. **Genuinely novel frameworks are rare.** Of the 30 analyzed:
- **4 frameworks** (Sliver, Havoc, Realm, TripleCross) demonstrate significant code originality
- **6 frameworks** show moderate originality (Wyrm, AdaptixC2, Emp3r0r, Merlin, NimPlant, GC2)
- **20 frameworks** rely heavily on shared code from the three source projects above, or implement techniques using the same well-known recipes
5. **HTTP C2 communications show the most behavioral convergence.** Three jitter formula families, shared User-Agent strings (the IE11 UA appears in Empire, Nuages, and Covenant), and common URL path patterns create fingerprinting opportunities.
@C2Workbench Hey! Thatโs us ๐๐
The install instructions look a little complicated - we usually recommend the steps in the README to get started locally or terraform apply for production.
Excited to share a sneak peek of Eldritch v2!
Weโve been rebuilding our automation language from scratch to make it stealthier and more modular. Try it out now!
https://t.co/X1cmPtPhkk
Realm now has global filters!
Filters can be applied to most views and stick with you throughout the experience making it easier to work with the same set of beacons or tasks.
https://t.co/vbtW3j1tzw
We've started a blog to document some of the design decisions we make throughout the development process! ๐
Our first posts highlights the new redirectors features and the challenges that app layer crypto posed.
Realm app layer crypto is here! ๐
Agents can be built with a server public key.
Transports leverage an ephemeral diffie-hellman key-exchange and xchacha for message encryption.
It's been a long time coming but it's finally here!
https://t.co/lt94x32ZJR
I had the privilege to red team @NationalCCDC this weekend. I had a great time and got to let AI control @Realm_C2 for the first ever AI powered service take down. ๐