Closed zoomequipd closed 3 years ago
They mention in the advisory: This file is a 64-bit DLL file identified as a custom Cobalt Strike Beacon Version 4 implant The configuration file is encoded via an XOR with the key 0x2e and a 16-bit byte swap. The parsed configuration file for the Cobalt Beacon implant is displayed below
We can't support custom beacons..
I believe Didier's 1768.py beacon parser is able to parse beacons XOR-encoded with a changing XOR key:
https://blog.didierstevens.com/2021/01/28/update-xorselection-1sc-version-6-0/amp/
Unfortunately, it complains of the filesize being too large, but wondered whether some of the capabilities could be incorporated into this parser. I've tried to understand what is happening in that script, but honestly I got lost looking at the code!
Description
Today, a CISA Mawlare Analysis Report was released which details the CS Beacon config of ee44c0692fd2ab2f01d17ca4b58ca6c7f79388cbc681f885bb17ec946514088c and provides a config (detailed below in Expected Output) which is different than the config extract when running
parse_beacon_config.py
Most fields are missing, thought it almost gets some of the fields, it seems to be missing a few while others appear to be jumbled.
Actual Output
Expected Output
(From CISA report)