<?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>Brother Industries, Ltd. — CraftedSignal Threat Feed</title><link>https://feed.craftedsignal.io/vendors/brother-industries-ltd./</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:31 +0000</lastBuildDate><atom:link href="https://feed.craftedsignal.io/vendors/brother-industries-ltd./feed.xml" rel="self" type="application/rss+xml"/><item><title>Process Created with an Elevated Token via Token Theft</title><link>https://feed.craftedsignal.io/briefs/2026-05-process-created-with-elevated-token/</link><pubDate>Tue, 12 May 2026 19:11:31 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2026-05-process-created-with-elevated-token/</guid><description>This rule detects the creation of a process running as SYSTEM while impersonating the token context of a Windows core binary, which adversaries may leverage to escalate privileges and bypass access controls through token theft.</description><content:encoded><![CDATA[<p>This detection rule identifies the creation of a process running as SYSTEM while impersonating the token context of a Windows core binary. The technique, often referred to as token theft, allows adversaries to escalate privileges and bypass access controls by creating a new process with a different token. The rule focuses on detecting instances where a process is initiated with the SYSTEM user ID (S-1-5-18) and its effective parent process is a privileged Microsoft native binary located in a standard Windows directory. This activity is indicative of an attempt to hijack a legitimate system process&rsquo;s token for malicious purposes. This can lead to full system compromise.</p>
<h2 id="attack-chain">Attack Chain</h2>
<ol>
<li>An attacker gains initial access to the system, potentially through phishing or exploiting a vulnerability.</li>
<li>The attacker identifies a privileged Windows process, such as a service running as SYSTEM, as a target for token theft.</li>
<li>The attacker uses the <code>CreateProcessWithTokenW</code> API (or similar) to create a new process.</li>
<li>The new process is configured to run under the security context (token) of the targeted privileged process.</li>
<li>The attacker then executes malicious code within the context of the newly created process.</li>
<li>This malicious code now operates with SYSTEM-level privileges, bypassing normal access controls.</li>
<li>The attacker can then use these elevated privileges to install malware, modify system settings, or steal sensitive data.</li>
<li>Finally, the adversary achieves persistence and control of the system.</li>
</ol>
<h2 id="impact">Impact</h2>
<p>Successful exploitation allows attackers to perform any action on the system with the highest privileges. This includes installing malware, accessing sensitive data, creating new user accounts with administrative rights, and disabling security controls. The impact is a complete compromise of the affected system. The Elastic rule has a risk score of 73 and is classified as high severity.</p>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li>Enable Elastic Defend to collect the necessary process creation events, as specified in the <a href="https://ela.st/install-elastic-defend">setup instructions</a>.</li>
<li>Deploy the provided Sigma rule to your SIEM to detect processes created with elevated tokens. Tune the rule based on observed false positives in your environment.</li>
<li>Investigate any alerts generated by the Sigma rule by examining the process tree, focusing on the <code>user.id</code>, <code>process.executable</code>, <code>process.parent.executable</code>, and <code>process.Ext.effective_parent.executable</code> fields as outlined in the rule&rsquo;s <code>note</code> section.</li>
<li>Review and validate any exceptions before implementing them, ensuring that the exact child/parent/effective-parent pattern is stable for the same host or managed host group, and avoid broad exceptions.</li>
</ul>
]]></content:encoded><category domain="severity">high</category><category domain="type">advisory</category><category>privilege-escalation</category><category>token-theft</category><category>windows</category></item></channel></rss>