<?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>Kalilinux — CraftedSignal Threat Feed</title><link>https://feed.craftedsignal.io/tags/kalilinux/</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>Tue, 02 Jan 2024 12:00:00 +0000</lastBuildDate><atom:link href="https://feed.craftedsignal.io/tags/kalilinux/feed.xml" rel="self" type="application/rss+xml"/><item><title>Detection of Kali Linux Installation or Usage via Windows Subsystem for Linux (WSL)</title><link>https://feed.craftedsignal.io/briefs/2024-01-kali-wsl-install/</link><pubDate>Tue, 02 Jan 2024 12:00:00 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2024-01-kali-wsl-install/</guid><description>Adversaries may attempt to install or use Kali Linux via Windows Subsystem for Linux (WSL) to avoid detection, potentially enabling them to perform malicious activities within a Windows environment while blending in with legitimate WSL usage.</description><content:encoded><![CDATA[<p>This detection identifies attempts to install or utilize Kali Linux through the Windows Subsystem for Linux (WSL). Attackers may leverage WSL to deploy Kali Linux as a means of circumventing traditional security measures and carrying out malicious operations within a Windows operating system. This behavior enables them to potentially blend their activities with legitimate WSL usage, making detection more challenging. The detection focuses on identifying specific processes and command-line arguments associated with Kali Linux installations and executions within the WSL environment, aiming to expose malicious actors utilizing this technique for nefarious purposes. This activity started being tracked in early 2023. Defenders should be aware of this technique, as it can be used to bypass security controls and perform malicious activities discreetly.</p>
<h2 id="attack-chain">Attack Chain</h2>
<ol>
<li>An attacker gains initial access to a Windows system through methods outside the scope of this specific detection (e.g., phishing, exploitation of a vulnerability).</li>
<li>The attacker enables WSL on the target Windows system using PowerShell or command-line tools.</li>
<li>The attacker downloads the Kali Linux distribution for WSL from the Microsoft Store or another source.</li>
<li>The attacker uses <code>wsl.exe</code> with arguments like <code>-d</code>, <code>--distribution</code>, <code>-i</code>, or <code>--install</code> along with &ldquo;kali*&rdquo; to install the Kali Linux distribution.</li>
<li>Alternatively, the attacker directly executes the <code>kali.exe</code> binary located within the Kali Linux package path (e.g., <code>C:\\Users\\*\\AppData\\Local\\packages\\kalilinux*</code>).</li>
<li>Once Kali Linux is installed, the attacker uses it to perform various malicious activities, such as penetration testing, vulnerability scanning, or exploiting other systems on the network.</li>
<li>The attacker may leverage tools and utilities within Kali Linux to escalate privileges, move laterally, or exfiltrate sensitive data.</li>
<li>The final objective is typically to compromise the target system or network, steal valuable information, or disrupt operations.</li>
</ol>
<h2 id="impact">Impact</h2>
<p>A successful attack using Kali Linux within WSL can lead to significant damage, including data breaches, system compromise, and disruption of services. The use of Kali Linux provides attackers with a wide range of tools and capabilities for reconnaissance, exploitation, and post-exploitation activities. Depending on the attacker&rsquo;s objectives, this can result in financial losses, reputational damage, and legal liabilities. Organizations across various sectors are vulnerable, as this technique can be used against any Windows system with WSL enabled.</p>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li>Deploy the Sigma rule &ldquo;Detect Kali Linux Installation via WSL&rdquo; to your SIEM to detect the use of <code>wsl.exe</code> with specific Kali Linux installation arguments (rule).</li>
<li>Deploy the Sigma rule &ldquo;Detect Kali Linux Executable via WSL&rdquo; to your SIEM to detect the direct execution of <code>kali.exe</code> from the common install directories (rule).</li>
<li>Monitor process creation events for the execution of <code>wsl.exe</code> and <code>kali.exe</code> within the Windows environment (logsource).</li>
<li>Review and restrict the usage of WSL within the organization to only authorized users and systems (overview).</li>
<li>Implement application control policies to prevent the execution of unauthorized binaries, including <code>kali.exe</code> (overview).</li>
</ul>
]]></content:encoded><category domain="severity">high</category><category domain="type">advisory</category><category>defense-evasion</category><category>windows</category><category>wsl</category><category>kalilinux</category></item></channel></rss>