<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>SMS — CraftedSignal Threat Feed</title><link>https://feed.craftedsignal.io/products/sms/</link><description>Trending threats, MITRE ATT&amp;CK coverage, and detection metadata. Fed continuously.</description><generator>Hugo</generator><language>en</language><managingEditor>hello@craftedsignal.io</managingEditor><webMaster>hello@craftedsignal.io</webMaster><lastBuildDate>Tue, 12 May 2026 19:11:50 +0000</lastBuildDate><atom:link href="https://feed.craftedsignal.io/products/sms/feed.xml" rel="self" type="application/rss+xml"/><item><title>Windows Service Installed via an Unusual Client for Privilege Escalation</title><link>https://feed.craftedsignal.io/briefs/2026-05-windows-service-privilege-escalation/</link><pubDate>Tue, 12 May 2026 19:11:50 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2026-05-windows-service-privilege-escalation/</guid><description>Identifies the creation of a Windows service by an unusual client process, which can be leveraged to escalate privileges from administrator to SYSTEM by exploiting misconfigurations or vulnerabilities in the service creation process.</description><content:encoded><![CDATA[<p>This detection identifies the creation of Windows services by unusual client processes. Adversaries may exploit this by creating services with administrator privileges, which then execute under SYSTEM privileges, allowing for privilege escalation. The rule focuses on detecting services installed with a ClientProcessId or ParentProcessId of 0, suggesting an unusual or potentially malicious service creation method. The rule also excludes known legitimate services such as VeeamVssSupport, VeeamLogShipper, PDQ Inventory, PDQ Deploy, CrowdStrike installer services, SCCM/SMS, nsnetpush and pbpsdeploy to minimize false positives. The tactic aims to escalate privileges within the Windows environment from administrator to SYSTEM level.</p>
<h2 id="attack-chain">Attack Chain</h2>
<ol>
<li>An attacker gains initial access to a system with administrator-level privileges.</li>
<li>The attacker uses a custom service control manager RPC client or another unusual method to create a new Windows service.</li>
<li>The ClientProcessId or ParentProcessId is set to 0 during service creation, indicating an unusual installation process.</li>
<li>The service is configured to run as LocalSystem, granting it highly privileged access.</li>
<li>The attacker configures the service to execute a malicious executable or script.</li>
<li>The service is started, either manually or automatically, by the operating system.</li>
<li>The malicious executable or script runs with SYSTEM privileges.</li>
<li>The attacker achieves privilege escalation, allowing them to perform actions that require the highest level of access.</li>
</ol>
<h2 id="impact">Impact</h2>
<p>Successful exploitation allows an attacker to escalate privileges from administrator to SYSTEM, granting them full control over the compromised system. This can lead to data theft, installation of malware, or complete system compromise. The impact is significant, as the attacker can bypass security controls and perform any action on the system with the highest level of privilege.</p>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li>Enable Audit Security System Extension to generate the necessary events for detection (reference: <a href="https://ela.st/audit-security-system-extension">https://ela.st/audit-security-system-extension</a>).</li>
<li>Deploy the Sigma rule &ldquo;Detect Windows Service Creation with Null Process ID&rdquo; to identify potentially malicious service installations. Tune the rule by adding legitimate software deployment tools to the exclusion list based on observed false positives in your environment.</li>
<li>Investigate any alerts generated by the Sigma rule by examining the ServiceFileName, ServiceAccount, and ClientProcessId to determine the legitimacy of the service creation event.</li>
<li>Monitor Event ID 4697 (A new service was installed in the system) in Windows Security Event Logs for unusual service creation events.</li>
</ul>
]]></content:encoded><category domain="severity">high</category><category domain="type">advisory</category><category>privilege-escalation</category><category>windows-service</category><category>windows</category></item></channel></rss>