<?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>Ryuk — CraftedSignal Threat Feed</title><link>https://feed.craftedsignal.io/actors/ryuk/</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/actors/ryuk/feed.xml" rel="self" type="application/rss+xml"/><item><title>Windows Defender Disabled via Registry Modification</title><link>https://feed.craftedsignal.io/briefs/2024-01-disable-antivirus-registry/</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-antivirus-registry/</guid><description>An attacker modifies the Windows Registry key 'DisableAntiSpyware' to disable Windows Defender, a technique commonly associated with Ryuk ransomware to evade defenses.</description><content:encoded><![CDATA[<p>This threat brief addresses the disabling of Windows Defender by modifying the <code>DisableAntiSpyware</code> registry key. This is a common tactic used by ransomware actors, including Ryuk, to disable endpoint protection and facilitate malicious activities. The modification involves setting the registry value <code>DisableAntiSpyware</code> to <code>0x00000001</code>. This activity is significant because it directly impairs a critical security control, potentially allowing attackers to deploy ransomware, exfiltrate data, or further compromise the system without interference from the endpoint antivirus. The registry modification is typically performed post-exploitation, after an attacker has already gained initial access and established a foothold. Defenders must monitor registry modifications to detect and prevent this form of defense evasion.</p>
<h2 id="attack-chain">Attack Chain</h2>
<ol>
<li>Initial access is gained through an exploit or compromised credentials.</li>
<li>The attacker executes code on the target system, potentially via PowerShell or cmd.exe.</li>
<li>The attacker identifies the <code>DisableAntiSpyware</code> registry key location.</li>
<li>The attacker uses <code>reg.exe</code> or PowerShell&rsquo;s <code>Set-ItemProperty</code> to modify the registry key <code>HKLM\SOFTWARE\Microsoft\Windows Defender\DisableAntiSpyware</code>.</li>
<li>The <code>DisableAntiSpyware</code> value is set to <code>0x00000001</code>, disabling Windows Defender.</li>
<li>The attacker verifies that Windows Defender is disabled by checking its status.</li>
<li>The attacker proceeds with lateral movement, privilege escalation, or data exfiltration without AV interference.</li>
<li>Finally, the attacker deploys ransomware, encrypting files and demanding ransom payment.</li>
</ol>
<h2 id="impact">Impact</h2>
<p>Successful disabling of Windows Defender allows attackers to operate unimpeded on the compromised system. This can lead to the complete encryption of critical files, resulting in significant data loss and operational disruption. Organizations affected by Ryuk ransomware have experienced substantial financial losses, reputational damage, and extensive recovery efforts. Disabling antivirus solutions is a common step in ransomware deployment, increasing the likelihood of a successful attack and maximizing the damage caused.</p>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li>Deploy the Sigma rule <code>Detect Windows Defender DisableAntiSpyware Registry Modification</code> to your SIEM to identify registry modifications indicative of this attack.</li>
<li>Enable Sysmon Event ID 13 logging to capture registry modification events on endpoints.</li>
<li>Investigate any alerts generated by the Sigma rule <code>Detect Suspicious Process Modifying Windows Defender Registry</code> to determine the legitimacy of the registry change.</li>
<li>Implement strict access control policies to prevent unauthorized registry modifications.</li>
<li>Monitor endpoints for unusual process behavior after the registry key is modified.</li>
</ul>
]]></content:encoded><category domain="severity">high</category><category domain="type">threat</category><category>defense-evasion</category><category>registry-modification</category><category>ransomware</category><category>windows</category></item></channel></rss>