Topline Takeaways
- Industry target: Government
- Attacker methods:
- Obfuscated PowerShell
- Linux C2 hosted in Finland
- Potential SolarMarker
- Recommended mitigations:
- Require the use of secure password managers.
- Employ least-privilege access controls.
- Implement strict controls on the use of scripting languages.
Incident Timeline for 2024-10-16
Blackpoint’s MDR technology alerted to obfuscated PowerShell on a device of a government partner. Blackpoint’s Active SOC isolated the impacted device and contacted the partner to inform them of the incident.
Initial investigation into the incident revealed that the obfuscated PowerShell first initialized a new Advanced Encryption Standard (AES) Encryption Service Provider Object and then set the AES Encryption Key. Once both the AES object and Key were created, it set the Initialization Vector. With the prerequisites set, default encrypted registry values located at HKCU:\Software\Classes\ were retrieved. Then using the previously set AES key and IV key, the PowerShell decoded those values and then loaded and executed the data into memory.
Further investigation revealed a malicious PowerShell callout to a Linux command and control (C2) hosted in Finland. While Blackpoint’s SOC was unable to validate the malware due to quick response and isolation, the activity aligns with a possible SolarMarker infection.
More About SolarMarker
SolarMarker is written in .NET, possesses a backdoor and information stealing capability, and has been active since 2021. SolarMarker has previously been reported to encrypt its traffic to C2 servers using hard-coded RSA keys and a symmetric AES CBC algorithm; data is often exfiltrated in a JSON format to the attackers C2 server.
The threat actor behind the SolarMarker malware has consistently made changes and improvements to avoid takedown and detection methods, making SolarMarker an attractive and competitive malware operation.
APG Threat Analysis for SolarMarker
Blackpoint’s Adversary Pursuit Group (APG) predicts the continued deployment of the SolarMarker malware to target organizations across all verticals over the next 12 months. This assessment is supported by the observation of similar incidents involving our partner in healthcare on April 05, 2024 and external reports related to the deployment of SolarMarker.
Mitigations
- Require the use of secure password managers to make accessing passwords by threat actors more difficult.
- Employ least-privilege access controls to ensure that users only have access to the data and resources required to complete their job functions.
- Implement strict controls on the use of scripting languages, as threat actors rely on scripting languages to deploy malware and conduct malicious activities.