<?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>Sidekick.vsto — CraftedSignal Threat Feed</title><link>https://feed.craftedsignal.io/products/sidekick.vsto/</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 14:00:00 +0000</lastBuildDate><atom:link href="https://feed.craftedsignal.io/products/sidekick.vsto/feed.xml" rel="self" type="application/rss+xml"/><item><title>Suspicious Execution via Microsoft Office Add-Ins</title><link>https://feed.craftedsignal.io/briefs/2024-01-office-addins/</link><pubDate>Wed, 03 Jan 2024 14:00:00 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2024-01-office-addins/</guid><description>This rule detects suspicious execution of Microsoft Office applications launching Office Add-Ins from unusual paths or with atypical parent processes, potentially indicating an attempt to gain initial access via a malicious phishing campaign.</description><content:encoded><![CDATA[<p>Attackers are increasingly leveraging malicious Microsoft Office Add-Ins to gain initial access and persistence on victim systems. These add-ins, often delivered through phishing campaigns, contain embedded malicious code. This detection identifies unusual execution patterns, such as Office applications (WINWORD.EXE, EXCEL.EXE, POWERPNT.EXE, MSACCESS.EXE, VSTOInstaller.exe) launching add-ins (wll, xll, ppa, ppam, xla, xlam, vsto) from suspicious paths like Temp or Downloads directories, or with atypical parent processes (explorer.exe, OpenWith.exe, cmd.exe, powershell.exe). The detection logic filters out known benign activities to minimize false positives, focusing on anomalies indicative of malicious intent, such as installations of Logitech software. This activity matters because successful exploitation can lead to arbitrary code execution, data theft, and further compromise of the victim&rsquo;s network.</p>
<h2 id="attack-chain">Attack Chain</h2>
<ol>
<li>A user receives a phishing email containing a malicious Microsoft Office document.</li>
<li>The user opens the document, which prompts them to enable macros or install an add-in.</li>
<li>The malicious add-in (wll, xll, ppa, ppam, xla, xlam, vsto) is downloaded from a remote server or dropped into a suspicious directory, such as %TEMP% or %APPDATA%.</li>
<li>The user executes an Office application (WINWORD.EXE, EXCEL.EXE, POWERPNT.EXE, MSACCESS.EXE), which loads the malicious add-in.</li>
<li>The malicious add-in executes arbitrary code, potentially downloading and executing a second-stage payload.</li>
<li>The add-in may establish persistence by modifying registry keys or creating scheduled tasks.</li>
<li>The attacker gains initial access to the system and can perform reconnaissance, lateral movement, and data exfiltration.</li>
<li>The attacker achieves their objective, which could include data theft, ransomware deployment, or intellectual property theft.</li>
</ol>
<h2 id="impact">Impact</h2>
<p>A successful attack can lead to complete system compromise, data theft, and potential ransomware deployment. Organizations across all sectors are at risk, particularly those with a high volume of email traffic. The use of malicious Office Add-Ins provides attackers with a persistent foothold within the victim&rsquo;s environment, allowing for long-term data collection and disruption of business operations. This can lead to significant financial losses, reputational damage, and legal liabilities.</p>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li>Deploy the Sigma rule <code>Office Add-In Loaded From Suspicious Path</code> to detect add-ins loaded from temporary or download directories based on <code>process.args</code> and <code>process.name</code>.</li>
<li>Deploy the Sigma rule <code>Office Add-In Loaded By Suspicious Parent</code> to detect add-ins loaded by <code>cmd.exe</code> or <code>powershell.exe</code> based on <code>process.parent.name</code>.</li>
<li>Investigate any instances of <code>VSTOInstaller.exe</code> executing with the <code>/Uninstall</code> argument, as this may indicate suspicious activity, correlating with the exclusion rule in the provided query.</li>
<li>Monitor for Office applications launching add-ins with parent processes of <code>explorer.exe</code> or <code>OpenWith.exe</code> using process creation logs and the provided query logic.</li>
<li>Implement stricter email filtering to prevent phishing emails containing malicious Office documents from reaching end-users.</li>
</ul>
]]></content:encoded><category domain="severity">medium</category><category domain="type">advisory</category><category>office-addins</category><category>phishing</category><category>initial-access</category></item></channel></rss>