XMRig - CraftedSignal Threat Feedhttps://feed.craftedsignal.io/actors/xmrig/Trending threats, MITRE ATT&CK coverage, and detection metadata. Fed continuously.Hugoenhello@craftedsignal.iohello@craftedsignal.ioWed, 03 Jan 2024 12:00:00 +0000Excessive Usage of SC Service Utilityhttps://feed.craftedsignal.io/briefs/2024-01-excessive-sc-usage/Wed, 03 Jan 2024 12:00:00 +0000hello@craftedsignal.iohttps://feed.craftedsignal.io/briefs/2024-01-excessive-sc-usage/Detection of anomalous usage of sc.exe, often abused by ransomware and malware to manipulate services for privilege escalation or disabling security measures.This detection identifies potentially malicious activity related to the excessive use of sc.exe, the Windows Service Control Manager command-line utility. Observed in various ransomware campaigns and malware such as XMRig, adversaries leverage sc.exe to create, modify, delete, or disable system services. These actions may target security applications to weaken defenses or be used for privilege escalation to gain elevated access. The detection logic analyzes process creation events for sc.exe, identifies outliers in its execution frequency, and highlights potentially malicious instances that deviate significantly from established baselines. This activity warrants investigation as it often precedes or accompanies more severe malicious actions.

Attack Chain

  1. Initial Access: Adversary gains access to the target system through unspecified means (e.g., exploitation, compromised credentials).
  2. Persistence: The adversary uses sc.exe to create a new service configured to execute a malicious payload upon system restart.
  3. Defense Evasion: sc.exe is used to disable or delete existing services, potentially including security software or logging mechanisms.
  4. Privilege Escalation: A vulnerable service is identified or created, and sc.exe is used to modify its configuration, allowing the adversary to execute code with elevated privileges.
  5. Execution: sc.exe is used to start the modified or newly created service, triggering the execution of the malicious payload.
  6. Lateral Movement: The adversary uses sc.exe combined with other tools (e.g., PsExec, WMI) to manage services on other systems in the network, facilitating lateral movement.
  7. Impact: Depending on the adversary's objective, the final impact could range from data exfiltration to system encryption (ransomware), achieved through services manipulated with sc.exe.

Impact

Compromise via excessive sc.exe usage can lead to significant disruption, including disabling critical security controls, escalating privileges, and enabling lateral movement across a network. Successful exploitation often results in malware deployment, data theft, or ransomware encryption. While specific victim numbers are not detailed in the source, the targeted sectors typically include organizations vulnerable to ransomware attacks. The impact of a successful attack includes data loss, financial damage, and reputational harm.

Recommendation

  • Enable Sysmon process creation logging (EventCode 1) to capture sc.exe executions for detection using the provided Sigma rules.
  • Deploy the Sigma rule "Excessive SC.exe Usage Detection" to your SIEM to detect anomalous sc.exe activity and tune thresholds based on your environment.
  • Investigate any alerts generated by the Sigma rule "SC.exe Service Manipulation" to identify potential malicious service modifications.
  • Filter benign usage of sc.exe using the "excessive_usage_of_sc_service_utility_filter" macro, customizing it with known-good software that legitimately uses the utility.
]]>mediumadvisoryendpointsc.exeservice_controlprivilege_escalationdefense_evasionransomwareExcessive Taskkill Usage for Defense Evasionhttps://feed.craftedsignal.io/briefs/2024-01-03-excessive-taskkill/Wed, 03 Jan 2024 12:00:00 +0000hello@craftedsignal.iohttps://feed.craftedsignal.io/briefs/2024-01-03-excessive-taskkill/Adversaries use excessive calls to `taskkill.exe` (more than 10 times within a minute) to disable security tools or critical processes, evading detection and compromising systems.This threat brief addresses the excessive use of taskkill.exe, a Windows command-line utility, by various threat actors to terminate processes on compromised systems. The observed behavior involves executing taskkill.exe more than ten times within a one-minute timeframe. This technique is employed to disable security software, terminate monitoring agents, and halt other critical processes that could hinder the attacker's objectives. The DFIR Report has documented similar tactics in SQL Server attacks, while Joe Sandbox analysis reveals the use of taskkill.exe in malicious payloads. Successful execution of this evasion tactic allows attackers to bypass security controls, maintain persistence, and potentially deploy further malicious payloads such as ransomware or data exfiltration tools. This behavior has been associated with multiple malware families including Azorult, AgentTesla, NjRAT, XMRig, Crypto Stealer and BlankGrabber Stealer.

Attack Chain

  1. Initial access is achieved through various means, such as exploiting vulnerabilities or social engineering techniques. (TA0001)
  2. The attacker gains a foothold on the system and executes malicious code, either directly or through a dropper. (TA0002)
  3. The attacker enumerates running processes to identify security tools, monitoring agents, or other critical processes to disable (T1057).
  4. The attacker uses taskkill.exe with appropriate arguments to terminate the identified processes. (T1562.001)
  5. The attacker repeats the taskkill.exe command multiple times in a short period (more than 10 times within a minute) to ensure the targeted processes are terminated (T1562.001).
  6. With security tools disabled, the attacker proceeds to perform malicious activities, such as data exfiltration or lateral movement. (TA0007, TA0008)
  7. The attacker may install persistence mechanisms to maintain access to the compromised system, taking advantage of the disabled security controls. (TA0003)
  8. The attacker achieves their final objective, such as data theft, ransomware deployment, or disruption of services. (TA0040)

Impact

Successful execution of this attack can lead to significant disruption and damage. Security tools being disabled results in the system becoming vulnerable to further attacks. Data exfiltration can lead to financial loss and reputational damage. Ransomware deployment can encrypt critical data, causing business interruption and financial loss. While exact victim numbers are unavailable, this technique is associated with multiple malware families, indicating widespread potential impact.

Recommendation

  • Deploy the provided Sigma rule Excessive Taskkill Execution Count to detect instances where taskkill.exe is executed excessively within a short timeframe.
  • Enable process monitoring with command-line logging to capture the execution of taskkill.exe and its arguments, which is required for the Sigma rule to function correctly.
  • Investigate any alerts generated by the Sigma rule Excessive Taskkill Execution Count to determine the legitimacy of the taskkill.exe execution and identify potential malicious activity.
  • Use the provided Splunk search query to identify instances of excessive taskkill.exe usage in your environment and correlate with other security events to identify potential compromises.
  • Implement network segmentation to limit the impact of lateral movement if an attacker successfully disables security tools.
  • Review and harden endpoint security configurations to prevent attackers from easily disabling security tools.
]]>highthreattaskkilldefense-evasionwindows