<?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>Smartscreen — CraftedSignal Threat Feed</title><link>https://feed.craftedsignal.io/tags/smartscreen/</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, 03 Jan 2024 12:00:00 +0000</lastBuildDate><atom:link href="https://feed.craftedsignal.io/tags/smartscreen/feed.xml" rel="self" type="application/rss+xml"/><item><title>Windows SmartScreen Disabled via Registry Modification</title><link>https://feed.craftedsignal.io/briefs/2024-01-disable-smartscreen/</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-disable-smartscreen/</guid><description>Attackers disable Windows SmartScreen protection by modifying specific registry keys to evade detection and facilitate malware deployment.</description><content:encoded><![CDATA[<p>Attackers may attempt to disable Windows SmartScreen to evade detection and deliver malware payloads. Windows SmartScreen provides a warning system against phishing and malware, so disabling it can significantly increase the risk of successful attacks. This is often done by Remote Access Trojans (RATs) to evade detection while downloading additional payloads. The technique involves modifying specific registry keys to turn off the SmartScreen feature. This allows attackers to bypass security measures designed to protect users from malicious software and phishing attempts.</p>
<h2 id="attack-chain">Attack Chain</h2>
<ol>
<li>Initial Access: The attacker gains initial access to the system through unspecified means, such as exploiting a vulnerability or using stolen credentials.</li>
<li>Privilege Escalation: The attacker escalates privileges if necessary to gain the required permissions to modify the registry.</li>
<li>Registry Modification: The attacker modifies the registry keys associated with SmartScreen to disable the protection. This includes setting the <code>SmartScreenEnabled</code> value under <code>HKCU\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\</code> or <code>EnableSmartScreen</code> under <code>HKLM\Microsoft\Windows\System\</code> to &ldquo;Off&rdquo; or &ldquo;0&rdquo;.</li>
<li>Persistence: The attacker may establish persistence to ensure that the SmartScreen remains disabled even after a reboot.</li>
<li>Payload Delivery: With SmartScreen disabled, the attacker downloads and executes malicious payloads, such as malware or RATs, without triggering security warnings.</li>
<li>Lateral Movement: The attacker may use the compromised system to move laterally within the network, targeting other systems and resources.</li>
<li>Data Exfiltration: The attacker exfiltrates sensitive data from the compromised system or network.</li>
</ol>
<h2 id="impact">Impact</h2>
<p>Disabling SmartScreen can lead to a significant increase in successful malware infections and phishing attacks. Users are no longer warned about potentially malicious files or websites, making them more vulnerable to exploitation. This can result in data breaches, financial losses, and reputational damage. While specific numbers are unavailable, the impact is potentially widespread across organizations that rely on Windows SmartScreen as a security measure.</p>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li>Monitor registry modifications for changes to the <code>SmartScreenEnabled</code> and <code>EnableSmartScreen</code> registry keys and values using the provided Sigma rule (<code>SmartScreenDisabledViaRegistry</code>).</li>
<li>Enable Sysmon Event ID 13 to collect registry modification events, which are necessary for the Sigma rule to function (<code>SmartScreenDisabledViaRegistry</code>).</li>
<li>Investigate any detected instances of SmartScreen being disabled to determine if the activity is malicious.</li>
<li>Implement strict access controls to prevent unauthorized users from modifying registry settings.</li>
<li>Regularly review and audit registry settings to ensure that SmartScreen is enabled and functioning correctly.</li>
<li>Deploy the Sigma rule in this brief to your SIEM and tune for your environment.</li>
</ul>
]]></content:encoded><category domain="severity">high</category><category domain="type">advisory</category><category>defense-evasion</category><category>registry-modification</category><category>smartscreen</category></item><item><title>Windows Defender SmartScreen Prompt Override via Registry Modification</title><link>https://feed.craftedsignal.io/briefs/2024-01-smartscreen-override/</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-smartscreen-override/</guid><description>Attackers modify the Windows registry to disable SmartScreen prompt overrides, potentially allowing users to bypass security warnings and execute harmful content, leading to system compromise.</description><content:encoded><![CDATA[<p>This threat brief focuses on a technique used to impair Windows Defender SmartScreen protection by modifying specific registry settings. The attack involves altering the &ldquo;PreventSmartScreenPromptOverride&rdquo; registry value to allow users to bypass SmartScreen warnings. This manipulation effectively disables a key security control, making systems more vulnerable to malware and phishing attacks. While specific threat actors are not attributed in the source, the technique is a common tactic used by various threat actors to weaken defenses before or during an attack. This technique has been observed as recently as January 2024. This matters to defenders because SmartScreen is a critical defense against drive-by downloads and malicious websites. Disabling it greatly increases the attack surface.</p>
<h2 id="attack-chain">Attack Chain</h2>
<ol>
<li><strong>Initial Access:</strong> The attacker gains initial access to the system through unspecified means (e.g., compromised credentials or exploitation of a vulnerability).</li>
<li><strong>Privilege Escalation (if needed):</strong> The attacker may need to escalate privileges to modify the registry.</li>
<li><strong>Registry Modification:</strong> The attacker modifies the registry value at <code>HKLM\Software\Policies\Microsoft\Edge\PreventSmartScreenPromptOverride</code> or <code>HKCU\Software\Policies\Microsoft\Edge\PreventSmartScreenPromptOverride</code>.</li>
<li><strong>Setting Value to 0:</strong> The attacker sets the <code>PreventSmartScreenPromptOverride</code> value to <code>0x00000000</code>, effectively disabling the prompt override prevention.</li>
<li><strong>SmartScreen Weakening:</strong> With the registry change in place, SmartScreen prompt overrides are allowed, reducing the effectiveness of the security feature.</li>
<li><strong>User Interaction:</strong> The attacker relies on user interaction (e.g., clicking a malicious link or opening a malicious file) to execute harmful content.</li>
<li><strong>Malware Execution:</strong> The user bypasses the SmartScreen warning, leading to the execution of malware or malicious code.</li>
<li><strong>System Compromise:</strong> The executed malware compromises the system, potentially leading to data theft, further exploitation, or other malicious activities.</li>
</ol>
<h2 id="impact">Impact</h2>
<p>The impact of a successful SmartScreen override can be significant. Systems become more vulnerable to malware and phishing attacks, potentially leading to widespread infections, data breaches, and financial losses. While the exact number of victims is unknown, any system where this registry modification occurs is at increased risk. This technique is particularly effective in organizations with less security awareness or where users may be more prone to bypassing security warnings.</p>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li>Enable Sysmon EventID 13 logging to monitor registry modifications as indicated by the <code>data_source</code> field.</li>
<li>Deploy the Sigma rule <code>Detect SmartScreen Prompt Override</code> to your SIEM and tune for your environment.</li>
<li>Monitor changes to the <code>PreventSmartScreenPromptOverride</code> registry setting specifically using the <code>registry_path</code> field in the provided search query.</li>
<li>Investigate any alerts triggered by the Sigma rule to determine if the registry modification is malicious based on the <code>description</code>.</li>
</ul>
]]></content:encoded><category domain="severity">high</category><category domain="type">advisory</category><category>defense-evasion</category><category>registry-modification</category><category>smartscreen</category></item></channel></rss>