Scans files and process memory for Cobalt Strike beacons and extracts their configuration.
CobaltStrikeScan is a security tool that scans files or Windows process memory for Cobalt Strike beacons, a post-exploitation framework used in cyber attacks. It detects beacons through DLL injection analysis or YARA signatures and extracts their configuration for forensic examination. The tool helps security professionals identify and analyze malicious activity in compromised systems.
Security analysts, incident responders, and threat hunters working on Windows environments who need to detect and investigate Cobalt Strike beacon infections.
It provides a portable, focused solution for beacon detection and configuration extraction, leveraging community-driven YARA signatures and memory analysis techniques to enhance defensive capabilities against advanced threats.
Scan files or process memory for CobaltStrike beacons and parse their configuration
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Focuses specifically on Cobalt Strike beacons using high-quality YARA signatures from community research like Neo23x0's Signature Base, ensuring accurate identification of v3 and v4 beacons.
Parses and displays the beacon's configuration when detected, providing key threat intelligence such as C2 servers and campaign IDs, as highlighted in the acknowledgments for forensic analysis.
Compiles into a static exe with dependencies embedded via Costura.Fody, making it easy to run on Windows systems without additional installations, as noted in the building instructions.
Supports scanning running processes, individual files, or entire directories for flexibility, with options like --scan-processes and --directory-scan for varied forensic scenarios.
Limited to 64-bit Windows OS with .NET Framework 4.6, excluding use on other platforms like Linux or macOS, which reduces its applicability in mixed environments.
Requires administrator or SeDebugPrivilege to scan process memory, as stated in requirements, which can hinder usage in locked-down or monitored systems without elevated access.
Building involves cloning with submodules (e.g., GetInjectedThreads) and setting the Active Solution Platform to x64, adding steps that may be cumbersome for non-developers or quick deployments.