Observed in Multiple Ransomware Families - CraftedSignal Threat Feedhttps://feed.craftedsignal.io/actors/observed-in-multiple-ransomware-families/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_evasionransomware