<?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>Token-Manipulation — CraftedSignal Threat Feed</title><link>https://feed.craftedsignal.io/tags/token-manipulation/</link><description>Trending threats, MITRE ATT&amp;CK coverage, and detection metadata — refreshed continuously.</description><generator>Hugo</generator><language>en</language><managingEditor>hello@craftedsignal.io</managingEditor><webMaster>hello@craftedsignal.io</webMaster><lastBuildDate>Wed, 24 Jan 2024 12:00:00 +0000</lastBuildDate><atom:link href="https://feed.craftedsignal.io/tags/token-manipulation/feed.xml" rel="self" type="application/rss+xml"/><item><title>Unusual Process Performing NewCredentials Logon</title><link>https://feed.craftedsignal.io/briefs/2024-01-newcreds-logon-process/</link><pubDate>Wed, 24 Jan 2024 12:00:00 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2024-01-newcreds-logon-process/</guid><description>Anomalous NewCredentials logon events triggered by uncommon processes may indicate access token manipulation for privilege escalation.</description><content:encoded><![CDATA[<p>The NewCredentials logon type in Windows allows a process to impersonate a user without initiating a new logon session. While legitimate uses exist, adversaries can abuse this mechanism to forge access tokens, enabling privilege escalation and bypassing security controls. This detection focuses on identifying unusual processes that perform NewCredentials logons, excluding common system paths and service accounts. This approach aims to highlight potential access token manipulation attacks that might otherwise go unnoticed. The rule specifically looks for authentication events on Windows systems where the logon type is NewCredentials and the LogonProcessName is Advapi, excluding events where the SubjectUserName ends with &lsquo;$&rsquo; (service accounts) and the process executable resides within Program Files or Program Files (x86) directories.</p>
<h2 id="attack-chain">Attack Chain</h2>
<ol>
<li>An attacker gains initial access to a system (e.g., through phishing or exploiting a vulnerability).</li>
<li>The attacker deploys or utilizes a tool capable of access token manipulation.</li>
<li>The malicious tool generates a NewCredentials logon event using <code>Advapi*</code>.</li>
<li>The tool attempts to impersonate a privileged user account.</li>
<li>The compromised process assumes the identity of the targeted user.</li>
<li>The attacker uses the elevated privileges to access sensitive resources or perform unauthorized actions.</li>
<li>The attacker attempts to move laterally to other systems within the network, leveraging the stolen credentials.</li>
<li>The attacker achieves their final objective, such as data exfiltration or system compromise.</li>
</ol>
<h2 id="impact">Impact</h2>
<p>Successful exploitation can lead to complete system compromise, data breaches, and lateral movement within the network. The risk score associated with this behavior is 47, indicating a notable level of concern. While the number of victims and targeted sectors is not specified, the potential impact of privilege escalation warrants immediate investigation and remediation.</p>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li>Deploy the &ldquo;First Time Seen NewCredentials Logon Process&rdquo; rule to your SIEM and tune for your environment to detect unusual processes performing NewCredentials logons.</li>
<li>Enable Audit Logon to generate the necessary events for the detection rule to function as described in the setup instructions [https://ela.st/audit-logon].</li>
<li>Review and update access control policies and token management practices to mitigate the risk of access token manipulation.</li>
<li>Consult threat intelligence sources to determine if the identified process or behavior is associated with known malicious activity or threat actors as documented in the reference [https://www.elastic.co/pt/blog/how-attackers-abuse-access-token-manipulation].</li>
</ul>
]]></content:encoded><category domain="severity">medium</category><category domain="type">advisory</category><category>privilege-escalation</category><category>token-manipulation</category><category>windows</category></item><item><title>SeDebugPrivilege Enabled by a Suspicious Process</title><link>https://feed.craftedsignal.io/briefs/2024-01-sedebugpriv-enabled/</link><pubDate>Wed, 03 Jan 2024 12:00:00 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2024-01-sedebugpriv-enabled/</guid><description>The rule identifies a process running with a non-SYSTEM account that enables the SeDebugPrivilege privilege, which can be used by adversaries to debug and modify other processes to escalate privileges and bypass access controls.</description><content:encoded><![CDATA[<p>This detection rule identifies processes running under non-SYSTEM accounts that enable the SeDebugPrivilege. This privilege, typically reserved for system-level tasks, allows a process to debug and modify other processes. Adversaries may enable SeDebugPrivilege to escalate their privileges and bypass access controls, potentially gaining unauthorized access to sensitive data or system resources. The rule aims to detect suspicious processes enabling this privilege, excluding known legitimate processes, to flag potential privilege escalation attempts. This rule was last updated on 2026-05-04.</p>
<h2 id="attack-chain">Attack Chain</h2>
<ol>
<li>An attacker gains initial access to a Windows system through various means (e.g., phishing, exploiting a vulnerability).</li>
<li>The attacker executes a malicious process on the compromised system.</li>
<li>The malicious process attempts to enable the SeDebugPrivilege.</li>
<li>Windows Security Auditing logs a &ldquo;Token Right Adjusted Events&rdquo; event, indicating that a process has enabled SeDebugPrivilege.</li>
<li>The detection rule identifies the event, filtering out known legitimate processes that may legitimately enable this privilege (e.g., msiexec.exe, taskhostw.exe).</li>
<li>The rule triggers an alert, indicating a potential privilege escalation attempt.</li>
<li>Security analysts investigate the alert to determine the legitimacy of the process enabling SeDebugPrivilege and the context of its execution.</li>
</ol>
<h2 id="impact">Impact</h2>
<p>Successful exploitation and enabling of SeDebugPrivilege can allow an attacker to debug and modify other processes, potentially gaining access to sensitive information, escalating privileges to SYSTEM level, and bypassing security controls. This can lead to a complete compromise of the affected system and potentially lateral movement to other systems on the network. The impact is high, especially in environments where sensitive data is processed or stored.</p>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li>Enable Audit Token Right Adjusted Events to ensure proper logging of SeDebugPrivilege usage as per the <a href="https://ela.st/audit-token-right-adjusted-events">setup instructions</a>.</li>
<li>Deploy the &ldquo;SeDebugPrivilege Enabled by a Suspicious Process&rdquo; Sigma rule to your SIEM to detect potential privilege escalation attempts.</li>
<li>Review and tune the exclusion list in the Sigma rule to minimize false positives, considering legitimate processes in your environment, as described in the <a href="#false-positive-analysis">False positive analysis</a>.</li>
<li>Investigate any alerts generated by the Sigma rule to determine the legitimacy of the process enabling SeDebugPrivilege.</li>
<li>Monitor systems for unauthorized access or lateral movement following the detection of SeDebugPrivilege enabling.</li>
</ul>
]]></content:encoded><category domain="severity">medium</category><category domain="type">advisory</category><category>privilege-escalation</category><category>token-manipulation</category><category>windows</category></item></channel></rss>