<?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>Transmission — CraftedSignal Threat Feed</title><link>https://feed.craftedsignal.io/products/transmission/</link><description>Trending threats, MITRE ATT&amp;CK coverage, and detection metadata. Fed continuously.</description><generator>Hugo</generator><language>en</language><managingEditor>hello@craftedsignal.io</managingEditor><webMaster>hello@craftedsignal.io</webMaster><lastBuildDate>Wed, 03 Jan 2024 15:00:00 +0000</lastBuildDate><atom:link href="https://feed.craftedsignal.io/products/transmission/feed.xml" rel="self" type="application/rss+xml"/><item><title>Generic Ransomware Detection on macOS</title><link>https://feed.craftedsignal.io/briefs/2024-01-ransomware-detection/</link><pubDate>Wed, 03 Jan 2024 15:00:00 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2024-01-ransomware-detection/</guid><description>This brief outlines a method for generically detecting ransomware on macOS by monitoring file I/O events and identifying the rapid creation of encrypted files by untrusted processes, as proposed by Objective-See.</description><content:encoded><![CDATA[<p>This research, published by Objective-See in April 2016, explores techniques for generic ransomware detection on macOS. The core concept revolves around monitoring file system events to identify processes rapidly creating encrypted files. The research highlights the increasing prevalence of ransomware, even on macOS, citing examples like KeRanger, which infected thousands of Mac users via a compromised version of Transmission. The author proposes a detection mechanism that leverages file I/O monitoring, encryption detection, and trust assessment of processes to identify and potentially block ransomware activity. The aim is to provide a proactive defense against new and unknown ransomware variants that evade traditional signature-based antivirus solutions. This research has version 1.0, meaning, likely room for improvement.</p>
<h2 id="attack-chain">Attack Chain</h2>
<ol>
<li>The user downloads and executes a malicious application, or a legitimate application compromised with ransomware (e.g., KeRanger in Transmission).</li>
<li>The ransomware component initiates, often after a period of dormancy.</li>
<li>The ransomware process begins enumerating files within the user&rsquo;s home directory (/Users) and potentially other locations like /Volumes.</li>
<li>For each targeted file, the ransomware process opens the file for reading and writing (O_RDWR).</li>
<li>The process reads the file content into memory.</li>
<li>The ransomware uses a cryptographic algorithm (e.g., libsodium) to encrypt the file content.</li>
<li>The encrypted content is written back to the file, overwriting the original data. The encrypted files may have a new extension, such as &ldquo;.encrypted&rdquo;.</li>
<li>A ransom note (e.g., README_FOR_DECRYPT.txt) is created in directories containing encrypted files, providing instructions for payment and decryption.</li>
</ol>
<h2 id="impact">Impact</h2>
<p>A successful ransomware attack can result in the complete loss of access to user data.  Organizations and individuals affected by ransomware face potential financial losses due to ransom payments, business disruption, and recovery costs. The research mentions that CryptoWall 3.0 ransomware operators made $325 million, highlighting the financial incentives driving ransomware development and deployment. The KeRanger ransomware infected thousands of Mac users.</p>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li>Deploy the Sigma rule <code>macOS Ransomware File Creation</code> to detect suspicious file modifications by untrusted processes within user directories based on file I/O events.</li>
<li>Monitor process creation events and correlate them with file modification events, specifically targeting processes not signed by Apple or baselined using the <code>Untrusted Process Creating Encrypted Files</code> Sigma rule.</li>
<li>Implement file integrity monitoring (FIM) on critical user directories to detect unauthorized file modifications, complementing the generic ransomware detection approach.</li>
</ul>
]]></content:encoded><category domain="severity">medium</category><category domain="type">advisory</category><category>ransomware</category><category>malware</category><category>macos</category></item></channel></rss>