<?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>Windows Defender SmartScreen App Install Control — CraftedSignal Threat Feed</title><link>https://feed.craftedsignal.io/products/windows-defender-smartscreen-app-install-control/</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/products/windows-defender-smartscreen-app-install-control/feed.xml" rel="self" type="application/rss+xml"/><item><title>Windows Defender SmartScreen App Install Control Disabled via Registry Modification</title><link>https://feed.craftedsignal.io/briefs/2024-01-disable-app-install-control/</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-app-install-control/</guid><description>Attackers modify the Windows Registry to disable Windows Defender SmartScreen App Install Control, potentially allowing the installation of malicious web-based applications without restrictions, leading to system compromise and sensitive information exposure.</description><content:encoded><![CDATA[<p>Attackers are disabling the Windows Defender SmartScreen App Install Control feature by modifying specific registry keys. This action circumvents a built-in Windows security control designed to prevent the installation of potentially malicious applications downloaded from the web. This allows for the installation of harmful applications without user prompts or restrictions, significantly increasing the risk of system compromise. This behavior, while not commonly seen in default configurations, allows for increased attack opportunities. The targeting scope includes Windows systems where the App Install Control feature is enabled, and success allows for further malicious payloads to be executed.</p>
<h2 id="attack-chain">Attack Chain</h2>
<ol>
<li>An attacker gains initial access to the system (e.g., through phishing or exploiting a vulnerability).</li>
<li>The attacker escalates privileges to gain administrative rights if necessary.</li>
<li>The attacker uses a command-line tool like <code>reg.exe</code> or PowerShell to modify the registry.</li>
<li>The attacker modifies the <code>ConfigureAppInstallControl</code> value under the <code>HKLM:\SOFTWARE\Microsoft\Windows Defender\SmartScreen</code> registry key.</li>
<li>The attacker sets the <code>ConfigureAppInstallControl</code> value to &ldquo;Anywhere&rdquo; or modifies <code>ConfigureAppInstallControlEnabled</code> to &ldquo;0x00000000&rdquo;.</li>
<li>The Windows Defender SmartScreen App Install Control is disabled.</li>
<li>The attacker downloads and executes a malicious application from the web.</li>
<li>The malicious application compromises the system, potentially leading to data theft or further malicious activities.</li>
</ol>
<h2 id="impact">Impact</h2>
<p>Disabling the App Install Control can lead to the installation of malware, potentially affecting a large number of systems. This can result in data breaches, financial loss, and reputational damage. If successful, the attackers gain the ability to bypass built-in security features, increasing the likelihood of a successful compromise.</p>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li>Enable Sysmon EventID 13 logging to monitor registry modifications (reference: Sysmon EventID 13 data source).</li>
<li>Deploy the Sigma rule provided in this brief to your SIEM to detect the modification of the specific registry keys related to App Install Control (reference: Sigma rule).</li>
<li>Investigate any alerts generated by this rule to determine if the activity is malicious.</li>
<li>Implement Group Policy settings to prevent users from modifying these registry keys (reference: <code>Registry.registry_path</code> and <code>Registry.registry_value_data</code> in the Sigma rule).</li>
</ul>
]]></content:encoded><category domain="severity">high</category><category domain="type">advisory</category><category>defense-evasion</category><category>registry-abuse</category><category>windows</category></item></channel></rss>