<?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>Trend Micro Security Agent — CraftedSignal Threat Feed</title><link>https://feed.craftedsignal.io/products/trend-micro-security-agent/</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/trend-micro-security-agent/feed.xml" rel="self" type="application/rss+xml"/><item><title>Microsoft Defender Tampering via Registry Modification</title><link>https://feed.craftedsignal.io/briefs/2024-01-defender-tampering/</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-defender-tampering/</guid><description>Adversaries may disable or tamper with Microsoft Defender features via registry modifications to evade detection and conceal malicious behavior on Windows systems.</description><content:encoded><![CDATA[<p>Attackers commonly disable or tamper with Microsoft Defender features to evade detection and conceal malicious behavior within compromised Windows environments. This is often achieved by modifying specific registry keys that control the behavior and functionality of Defender components, such as real-time monitoring, exploit protection, and tamper protection itself. Such actions can significantly reduce the effectiveness of endpoint security, allowing malicious activities to proceed undetected. The references point to techniques that disable PUA protection, tamper protection, memory integrity, and real-time protection. This behavior is observed across various attack scenarios, including ransomware deployment and cryptocurrency mining campaigns.</p>
<h2 id="attack-chain">Attack Chain</h2>
<ol>
<li>Initial access is gained through an unspecified vector (e.g., phishing, exploitation of a vulnerability).</li>
<li>The attacker obtains elevated privileges on the system.</li>
<li>The attacker uses an administrative tool like <code>reg.exe</code> or PowerShell to modify the registry.</li>
<li>The attacker disables real-time monitoring by setting <code>HKLM\SOFTWARE\Policies\Microsoft\Windows Defender\Real-Time Protection\DisableRealtimeMonitoring</code> to 1.</li>
<li>The attacker disables tamper protection by setting <code>HKLM\SOFTWARE\Policies\Microsoft\Windows Defender\Features\TamperProtection</code> to 0.</li>
<li>The attacker disables PUA Protection by setting <code>HKLM\SOFTWARE\Policies\Microsoft\Windows Defender\PUAProtection</code> to 0.</li>
<li>With Defender weakened, the attacker executes malicious payloads, such as ransomware or cryptocurrency miners.</li>
</ol>
<h2 id="impact">Impact</h2>
<p>Successful tampering with Microsoft Defender can lead to a significant degradation of endpoint security posture. This can result in undetected malware infections, data breaches, and system compromise. Disabling Defender features can allow attackers to establish persistence, escalate privileges, and deploy malicious payloads without triggering alerts. The impact can range from individual system compromise to widespread network infection, depending on the attacker&rsquo;s objectives and the extent of the tampering.</p>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li>Deploy the Sigma rule &ldquo;Microsoft Windows Defender Tampering - Disable Realtime Monitoring&rdquo; to your SIEM to detect modifications to the <code>DisableRealtimeMonitoring</code> registry value.</li>
<li>Deploy the Sigma rule &ldquo;Microsoft Windows Defender Tampering - Disable Tamper Protection&rdquo; to detect modifications to the <code>TamperProtection</code> registry value.</li>
<li>Monitor registry modification events, specifically targeting keys associated with Microsoft Defender settings as described in the rule query.</li>
<li>Investigate any process modifying Windows Defender registry settings that are not explicitly authorized, referencing the process exclusions in the rule query.</li>
</ul>
]]></content:encoded><category domain="severity">medium</category><category domain="type">advisory</category><category>defense-evasion</category><category>registry-modification</category><category>windows</category></item></channel></rss>