Threat Intel
Cobalt Strike Beacon Extractor Tool Enables Rapid In‑Cluster Configuration Retrieval
A new Python utility scans Elastic Endpoint logs for Cobalt Strike memory dumps, extracts beacon configuration, and re‑indexes the data in ECS format. Defenders can run it via Docker and feed the results into existing playbooks.
Security teams can now pull Cobalt Strike beacon configuration directly from Elasticsearch alert data.
What happened
A Python utility, “Cobalt Strike Beacon Extractor,” was released to scan Elastic Endpoint logs for memory‑dumped CS beacons, parse the implant configuration, and re‑index the data in ECS format.
How it works
- Collects documents flagged by the CS memory‑dump detector.
- Runs the built‑in
cobaltstrike-config-extractoragainst the payload. - Normalises the output into an ECS‑compatible JSON document.
- Writes the result back to the same or a different Elasticsearch cluster.
Impact
Defenders who already ingest Elastic Endpoint data can immediately surface beacon details without exporting or parsing raw memory dumps.
What to do
- Deploy the Docker image:
docker run -ti --rm -v "$(pwd)/config.local.yml:/config.yml" cobalt-strike-extractor:latest -c /config.yml -v. - Configure
config.local.ymlwith your cluster’scloud.idand credentials. - Use Fleet policies to forward CS memory alerts to the extractor.
- Query the new index for
cobalt_strike_configdocuments and feed them into playbooks or SIEM dashboards.