<?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>Cryptocurrency-Mining — CraftedSignal Threat Feed</title><link>https://feed.craftedsignal.io/tags/cryptocurrency-mining/</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/tags/cryptocurrency-mining/feed.xml" rel="self" type="application/rss+xml"/><item><title>Detection of Process Termination via File Path Using WMIC</title><link>https://feed.craftedsignal.io/briefs/2024-01-03-process-kill-file-path/</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-03-process-kill-file-path/</guid><description>This analytic detects the use of `wmic.exe` with the `delete` command to terminate a process by specifying its executable path, often used to disable security tools or critical processes during the setup of malicious activities like cryptocurrency mining.</description><content:encoded><![CDATA[<p>This detection focuses on identifying the use of the Windows Management Instrumentation Command-line (WMIC) utility to terminate processes by referencing their file paths. Specifically, it looks for instances where <code>wmic.exe</code> is used with the <code>delete</code> command targeting an executable path. This technique is often employed by attackers to disable security software, terminate competing processes (such as other miners), or halt critical system services, as seen in cases involving cryptocurrency miners. The activity is often associated with the initial stages of setting up malicious operations on an endpoint, giving defenders an opportunity to disrupt attacks early in the kill chain. The source material was released in 2026, but the underlying technique has been used since at least 2020.</p>
<h2 id="attack-chain">Attack Chain</h2>
<ol>
<li>An attacker gains initial access to the system, often through methods not directly covered by this detection (e.g., exploiting a vulnerability or using compromised credentials).</li>
<li>The attacker executes <code>wmic.exe</code> with specific parameters to target a running process.</li>
<li>The command includes the <code>process</code> argument to specify the process to be targeted, the <code>executablepath</code> argument to identify the process by its file path, and the <code>delete</code> command to terminate the process.</li>
<li><code>wmic.exe</code> attempts to locate the process based on the provided file path.</li>
<li>If the process is found, <code>wmic.exe</code> sends a termination signal to the process.</li>
<li>The targeted process is terminated.</li>
<li>The attacker repeats this process to disable other security tools or competing processes.</li>
<li>The attacker proceeds with their primary objective, such as deploying and executing a cryptocurrency miner or establishing persistence.</li>
</ol>
<h2 id="impact">Impact</h2>
<p>Successful execution of this technique can lead to the disabling of security software, allowing malware to operate unimpeded. It can also result in the termination of critical system processes, leading to system instability or data loss. Observed cases include the deployment of XMRig cryptocurrency miners following the termination of security tools. If left unchecked, this activity can significantly increase the attacker&rsquo;s foothold within the compromised environment, facilitating further malicious actions.</p>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li>Deploy the Sigma rule <code>Detect Process Termination via WMIC File Path</code> to your SIEM and tune it for your environment to identify malicious process termination attempts.</li>
<li>Enable Sysmon process creation logging (Event ID 1) and Windows Event Log Security (4688) to provide the necessary data for the Sigma rules.</li>
<li>Investigate any identified instances of <code>wmic.exe</code> being used with the <code>delete</code> command, especially when targeting executable paths of known security products or critical system processes.</li>
<li>Implement the <code>process_kill_base_on_file_path_filter</code> macro referenced in the search query to reduce noise.</li>
</ul>
]]></content:encoded><category domain="severity">high</category><category domain="type">advisory</category><category>process-termination</category><category>wmic</category><category>cryptocurrency-mining</category><category>endpoint</category></item></channel></rss>