<?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>Application-Uninstall — CraftedSignal Threat Feed</title><link>https://feed.craftedsignal.io/tags/application-uninstall/</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/application-uninstall/feed.xml" rel="self" type="application/rss+xml"/><item><title>Suspicious WMIC Application Uninstallation</title><link>https://feed.craftedsignal.io/briefs/2024-01-wmic-uninstallation/</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-wmic-uninstallation/</guid><description>This analytic identifies the use of the WMIC command-line tool to uninstall applications non-interactively, a technique used to evade detection by removing security software, as observed in IcedID campaigns.</description><content:encoded><![CDATA[<p>This detection focuses on the abuse of Windows Management Instrumentation Command-line (WMIC) to uninstall applications in a non-interactive manner. This technique is often employed by threat actors, including IcedID, to disable or remove security software, such as antivirus solutions, in order to evade detection and establish a stronger foothold within a compromised environment. This activity is often seen post-compromise, after initial access has been established, and is used to further the attacker&rsquo;s objectives. The use of the <code>/nointeractive</code> flag is a key indicator of this malicious activity. This behavior is significant because it allows attackers to disable security defenses, facilitating further compromise and persistence within the environment.</p>
<h2 id="attack-chain">Attack Chain</h2>
<ol>
<li>Initial access is gained through a phishing campaign or other exploit.</li>
<li>The attacker executes a malicious payload on the victim machine.</li>
<li>The payload establishes persistence and elevates privileges.</li>
<li>WMIC is invoked via <code>wmic.exe</code> with parameters to enumerate installed products.</li>
<li>The attacker uses the <code>product</code> argument with a <code>where name</code> clause to identify target applications.</li>
<li>WMIC is then used with the <code>call uninstall</code> command to remove the target application.</li>
<li>The <code>/nointeractive</code> flag is used to suppress prompts and execute the uninstall silently.</li>
<li>Security software is disabled, allowing for further malicious activity.</li>
</ol>
<h2 id="impact">Impact</h2>
<p>Successful execution of this attack results in the removal of security software, such as antivirus or endpoint detection and response (EDR) agents, which significantly reduces the victim&rsquo;s ability to detect and respond to the compromise. As seen in the IcedID campaign, this can lead to rapid escalation, such as ransomware deployment within 24 hours. This can affect any Windows environment where WMIC is accessible, potentially impacting organizations of any size.</p>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li>Deploy the Sigma rule <code>Suspicious WMIC Product Uninstall via CommandLine</code> to detect non-interactive uninstallation attempts.</li>
<li>Investigate any process that spawns <code>wmic.exe</code> with arguments containing <code>product</code>, <code>where name</code>, <code>call uninstall</code>, and <code>/nointeractive</code>, as highlighted in the rule description.</li>
<li>Ensure endpoint detection and response (EDR) agents are configured to log process command-line arguments, which is required for the detection to function correctly.</li>
<li>Review and harden endpoint security policies to restrict the use of WMIC where possible.</li>
<li>Monitor parent processes of <code>wmic.exe</code> to identify potential malicious origins.</li>
<li>Whitelist legitimate uses of <code>wmic.exe</code> for application uninstallation, based on parent process and command line, to reduce false positives.</li>
</ul>
]]></content:encoded><category domain="severity">high</category><category domain="type">threat</category><category>defense-evasion</category><category>application-uninstall</category><category>wmic</category></item></channel></rss>