https://feed.craftedsignal.io/tags/beacon/Trending threats, MITRE ATT&CK coverage, and detection metadata — refreshed continuously.Hugoenhello@craftedsignal.iohello@craftedsignal.ioWed, 03 Jan 2024 12:00:00 +0000https://feed.craftedsignal.io/briefs/2024-01-powgoop-beacon/Wed, 03 Jan 2024 12:00:00 +0000hello@craftedsignal.iohttps://feed.craftedsignal.io/briefs/2024-01-powgoop-beacon/This detection identifies a DLL decoding and executing the PowGoop config.txt payload, indicating a stage in the MuddyWater infection chain where an obfuscated PowerShell beacon is unwrapped and live C2 communication starts.The detection identifies a specific stage in the MuddyWater (also known as SeedWorm, Static Kitten, and MERCURY) infection chain, focusing on the execution of the PowGoop loader. MuddyWater has been actively using PowGoop since at least 2020 as their primary initial access method. PowGoop abuses DLL side-loading, specifically targeting a fake GoogleUpdate.exe, to initiate a multi-stage decoding process. This ultimately leads to the deployment of a fully functional PowerShell backdoor disguised with a benign extension. The backdoor uses a config.txt file that contains a hardcoded C2 address and victim GUID. The malware beacons via modified base64-encoded HTTP, attempting to blend C2 traffic with legitimate Google Update processes to evade network-based detections.

Attack Chain

1. Initial access is achieved through an unknown vector (e.g., spearphishing) leading to the execution of a malicious DLL.
2. The malicious DLL is sideloaded by a fake GoogleUpdate.exe, masquerading as a legitimate Google application.
3. The DLL initiates a multi-stage decoding chain to decrypt and execute a PowerShell script.
4. The PowerShell script reads a config.txt file containing a hardcoded C2 address and victim GUID.
5. The PowerShell script decodes the C2 address from the config file to establish command and control.
6. PowerShell uses FromBase64String to decode the payload.
7. The PowerShell backdoor establishes persistence and begins beaconing to the C2 server via modified base64-encoded HTTP requests.
8. The attacker uses the established C2 channel to perform reconnaissance, lateral movement, and data exfiltration.

Impact

A successful PowGoop infection allows MuddyWater to gain persistent access to the compromised system. This access can be leveraged for a variety of malicious activities, including data theft, espionage, and further propagation of malware within the network. MuddyWater has been linked to numerous cyber espionage campaigns targeting government and commercial entities, particularly in the Middle East. The group’s activities pose a significant risk to organizations seeking to protect sensitive information and maintain operational integrity.

Recommendation

• Enable Sysmon Event ID 1 (process creation) logging to capture the necessary process execution details for the Sigma rules provided.
• Deploy the Sigma rules in this brief to your SIEM and tune for your environment.
• Investigate any PowerShell processes spawned by rundll32.exe that decode base64 strings and reference config.txt, as highlighted in the rule “Detect Windows PowGoop Beacon Decoding via CommandLine”.
• Monitor network traffic for base64-encoded HTTP requests originating from the Google Update process, as this is a technique used by PowGoop to mask C2 communications.

]]>highthreatmuddywaterpowgoopdll-sideloadingpowershellc2beaconhttps://feed.craftedsignal.io/briefs/2024-01-cobalt-strike-powershell-beacon/Wed, 03 Jan 2024 12:00:00 +0000hello@craftedsignal.iohttps://feed.craftedsignal.io/briefs/2024-01-cobalt-strike-powershell-beacon/This brief outlines detection strategies for default Cobalt Strike PowerShell beacons, which are used for command and control, by identifying specific function and variable names within PowerShell script block logs.Cobalt Strike is a popular commercial penetration testing tool often abused by threat actors for command and control (C2) after initial compromise. This brief focuses on detecting the default PowerShell beacon component of Cobalt Strike, which uses recognizable function and variable names in its scripts. By identifying these default names within PowerShell script block logs, defenders can detect Cobalt Strike activity even if the initial delivery mechanism is unknown. This detection is focused on the default variable names and function names within the tool and as such more sophisticated users of the tool may modify their scripts to evade this detection. This brief will aid in detecting default Cobalt Strike PowerShell beacons, giving defenders a chance to respond quickly.

Attack Chain

1. The attacker gains initial access to a target system through various means (e.g., spear phishing, exploiting a vulnerability).
2. A PowerShell script is executed on the target system, either through direct execution or by being called from another process (cmd.exe, mshta.exe).
3. The PowerShell script contains default Cobalt Strike PowerShell beacon code, including functions and variables like func_get_proc_address, $var_unsafe_native_methods, $var_gpa.Invoke, func_get_delegate_type, and $var_type_builder.
4. The script uses these functions and variables to dynamically load and execute malicious code in memory, bypassing traditional file-based antivirus solutions.
5. The beacon establishes a connection to the attacker’s C2 server, allowing for remote command execution.
6. The attacker uses the C2 connection to perform reconnaissance, move laterally within the network, and escalate privileges.
7. The attacker deploys additional tools or malware to achieve their objectives, such as data exfiltration or ransomware deployment.
8. The attacker maintains persistence on the compromised system to ensure continued access.

Impact

Successful exploitation via Cobalt Strike can lead to a complete compromise of the targeted system and potentially the entire network. Attackers can steal sensitive data, deploy ransomware, disrupt business operations, and cause significant financial and reputational damage. While the exact number of victims is unknown, Cobalt Strike is used in a wide range of attacks across various sectors, including healthcare, finance, and government. A successful attack could lead to significant data breaches, system downtime, and regulatory fines.

Recommendation

• Enable PowerShell script block logging (Event ID 4104) on all Windows endpoints to capture the necessary data for detection.
• Deploy the Sigma rule “Detect Default Cobalt Strike PowerShell Beacon” to your SIEM and tune for your environment using the included false positive guidance.
• Investigate any alerts generated by the Sigma rule, paying close attention to the parent processes and network connections associated with the PowerShell scripts.
• Implement network segmentation to limit the lateral movement of attackers within the network after initial compromise.
• Review and update PowerShell execution policies to prevent the execution of unsigned or untrusted scripts.

]]>highadvisorycobaltstrikepowershellbeaconcommandandcontrolwindows