<?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>Teams — CraftedSignal Threat Feed</title><link>https://feed.craftedsignal.io/products/teams/</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>Thu, 05 Sep 2024 14:17:05 +0000</lastBuildDate><atom:link href="https://feed.craftedsignal.io/products/teams/feed.xml" rel="self" type="application/rss+xml"/><item><title>Persistence via Windows Installer (Msiexec)</title><link>https://feed.craftedsignal.io/briefs/2024-09-msiexec-persistence/</link><pubDate>Thu, 05 Sep 2024 14:17:05 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2024-09-msiexec-persistence/</guid><description>Adversaries may establish persistence by abusing the Windows Installer (msiexec.exe) to create scheduled tasks or modify registry run keys, allowing for malicious code execution upon system startup or user logon.</description><content:encoded><![CDATA[<p>The Windows Installer (msiexec.exe) is a legitimate system tool used for installing, updating, and removing software on Windows systems. Adversaries can abuse msiexec.exe to establish persistence mechanisms by creating malicious scheduled tasks or modifying registry run keys. This allows them to execute arbitrary code during system startup or user logon. This technique is attractive to attackers due to msiexec.exe being a trusted Windows binary, potentially evading detection by security solutions that focus on flagging unknown or suspicious processes. The use of msiexec.exe for persistence can be difficult to detect without specific monitoring rules, as it is a common and legitimate system process. This activity can be observed across various Windows versions and is frequently integrated into automated attack frameworks and scripts.</p>
<h2 id="attack-chain">Attack Chain</h2>
<ol>
<li>An attacker gains initial access to a compromised system, potentially through phishing, exploitation of a vulnerability, or stolen credentials.</li>
<li>The attacker leverages msiexec.exe to create a new scheduled task using the <code>schtasks.exe</code> command, setting it to execute a malicious script or binary.</li>
<li>Alternatively, the attacker uses msiexec.exe in conjunction with <code>reg.exe</code> or PowerShell to modify registry keys under <code>HKLM\Software\Microsoft\Windows\CurrentVersion\Run</code> or <code>HKCU\Software\Microsoft\Windows\CurrentVersion\Run</code>, adding a pointer to their malicious executable.</li>
<li>The created scheduled task or registry entry points to a malicious payload, such as a reverse shell or a downloader.</li>
<li>The system is restarted, or the user logs on, triggering the execution of the newly created scheduled task or the malicious binary through the modified registry run key.</li>
<li>The malicious payload executes, establishing a persistent foothold for the attacker on the compromised system.</li>
<li>The attacker can now perform further actions, such as data exfiltration, lateral movement, or deployment of ransomware.</li>
</ol>
<h2 id="impact">Impact</h2>
<p>Successful exploitation allows the adversary to maintain persistent access to the compromised system. This can lead to data theft, system compromise, deployment of ransomware, or use of the system as a staging point for further attacks within the network. A single compromised system can be used to pivot and compromise additional systems, leading to a widespread security breach. The impact can include financial losses, reputational damage, and disruption of business operations.</p>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li>Monitor process creation events for msiexec.exe spawning <code>schtasks.exe</code> or <code>reg.exe</code> to create scheduled tasks or modify registry run keys (reference: rules in this brief).</li>
<li>Implement and tune the Sigma rules provided in this brief to detect suspicious msiexec.exe activity related to persistence mechanisms.</li>
<li>Review and audit existing scheduled tasks and registry run keys for any suspicious entries or anomalies.</li>
<li>Enable file integrity monitoring (FIM) on critical system directories, including the Windows Task Scheduler directory and registry run key locations (reference: event.category == &ldquo;file&rdquo; and file.path &hellip; and event.category == &ldquo;registry&rdquo; and registry.path &hellip; in the rule query).</li>
<li>Implement application control policies to restrict the execution of unauthorized or unknown executables (reference: rule query).</li>
</ul>
]]></content:encoded><category domain="severity">medium</category><category domain="type">advisory</category><category>persistence</category><category>defense-evasion</category><category>windows</category></item><item><title>Potential Masquerading as Communication Apps</title><link>https://feed.craftedsignal.io/briefs/2024-01-masquerading-communication-apps/</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-masquerading-communication-apps/</guid><description>Attackers may attempt to evade defenses by masquerading malicious processes as legitimate communication applications such as Slack, WebEx, Teams, Discord, RocketChat, Mattermost, WhatsApp, Zoom, Outlook and Thunderbird.</description><content:encoded><![CDATA[<p>Attackers may attempt to evade defenses by masquerading malicious processes as legitimate communication applications. This involves using names and icons that resemble trusted applications like Slack, WebEx, Teams, Discord, RocketChat, Mattermost, WhatsApp, Zoom, Outlook and Thunderbird to trick users and bypass security measures. This technique can be used to conceal malicious activity, bypass allowlists, or trick users into executing malware. The detection rule identifies suspicious instances by checking for unsigned or improperly signed processes, ensuring they match known trusted signatures, which helps in flagging potential threats that mimic trusted communication tools.</p>
<h2 id="attack-chain">Attack Chain</h2>
<ol>
<li>An attacker gains initial access to a Windows system through various means such as phishing or exploiting a vulnerability.</li>
<li>The attacker deploys a malicious executable onto the compromised system.</li>
<li>The attacker renames the malicious executable to resemble a legitimate communication application, such as &ldquo;slack.exe&rdquo; or &ldquo;Teams.exe&rdquo;.</li>
<li>The attacker modifies or removes the code signature of the malicious executable to avoid detection based on trusted publishers.</li>
<li>The attacker executes the renamed and potentially unsigned malicious executable.</li>
<li>The masqueraded process performs malicious actions, such as establishing a reverse shell or downloading additional payloads.</li>
<li>The attacker uses the compromised system to move laterally within the network, escalating privileges and compromising additional systems.</li>
<li>The final objective is to exfiltrate sensitive data or deploy ransomware.</li>
</ol>
<h2 id="impact">Impact</h2>
<p>Successful masquerading attacks can lead to significant security breaches, including data theft, system compromise, and financial loss. By disguising malicious processes as legitimate communication apps, attackers can bypass security controls and operate undetected for extended periods. This can result in widespread damage and disruption, as well as reputational damage for the targeted organization. The impact can range from a few compromised systems to a complete network takeover, depending on the attacker&rsquo;s objectives and the effectiveness of the masquerading technique.</p>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li>Deploy the Sigma rule &ldquo;Potential Masquerading as Communication Apps - Generic&rdquo; to your SIEM and tune for your environment to detect unsigned or improperly signed communication applications.</li>
<li>Deploy the Sigma rule &ldquo;Potential Masquerading as Communication Apps - Specific&rdquo; to your SIEM and tune for your environment to detect unsigned or improperly signed instances of specific communication applications.</li>
<li>Enable process creation logging on Windows systems to capture the necessary events for the Sigma rules.</li>
<li>Review and validate the code signatures of all communication apps on your systems to ensure they are properly signed by trusted entities.</li>
<li>Implement application control policies to restrict the execution of unsigned or untrusted executables.</li>
</ul>
]]></content:encoded><category domain="severity">medium</category><category domain="type">advisory</category><category>defense-evasion</category><category>masquerading</category><category>windows</category></item><item><title>Masquerading Business Application Installers</title><link>https://feed.craftedsignal.io/briefs/2024-01-masquerading-business-apps/</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-masquerading-business-apps/</guid><description>Attackers masquerade malicious executables as legitimate business application installers to trick users into downloading and executing malware, leveraging defense evasion and initial access techniques.</description><content:encoded><![CDATA[<p>Attackers often attempt to trick users into downloading and executing malicious executables by disguising them as legitimate business applications. This tactic is used to bypass security measures and gain initial access to a system. These malicious executables, often distributed via malicious ads, forum posts, and tutorials, mimic the names of commonly used applications such as Slack, WebEx, Teams, Discord, and Zoom. The executables are typically unsigned or signed with invalid certificates to further evade detection. This allows the attacker to execute arbitrary code on the victim&rsquo;s machine, potentially leading to further compromise. This campaign aims to target end-users who are less security-aware, and this makes social engineering attacks like this very effective.</p>
<h2 id="attack-chain">Attack Chain</h2>
<ol>
<li>The user visits a compromised website or clicks on a malicious advertisement.</li>
<li>The user is prompted to download an installer file masquerading as a legitimate business application (e.g., Slack, Zoom, Teams) from a download directory.</li>
<li>The downloaded executable is placed in the user&rsquo;s Downloads folder (e.g., C:\Users*\Downloads*).</li>
<li>The user executes the downloaded file.</li>
<li>The executable, lacking a valid code signature, begins execution.</li>
<li>The malicious installer may drop and execute additional malware components.</li>
<li>The malware establishes persistence, potentially using techniques such as registry key modification.</li>
<li>The malware performs malicious activities, such as data exfiltration or lateral movement.</li>
</ol>
<h2 id="impact">Impact</h2>
<p>Successful execution of a masqueraded business application installer can lead to a complete system compromise. The attacker gains initial access and can deploy various malware payloads, including ransomware, keyloggers, and data stealers. This can result in data breaches, financial loss, and reputational damage. Although the specific number of victims and sectors targeted are not detailed, the widespread use of the applications being spoofed (Slack, Zoom, etc.) suggests a broad potential impact.</p>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li>Implement the Sigma rule <code>Potential Masquerading as Business App Installer</code> to detect unsigned executables resembling legitimate business applications in download directories.</li>
<li>Enable process creation logging to capture the execution of unsigned executables.</li>
<li>Educate users on the risks of downloading and executing files from untrusted sources.</li>
<li>Implement application whitelisting to restrict the execution of unauthorized applications.</li>
<li>Regularly update endpoint detection and response (EDR) tools to detect and prevent the execution of known malware.</li>
<li>Monitor process execution events for processes originating from the Downloads folder that lack valid code signatures.</li>
</ul>
]]></content:encoded><category domain="severity">medium</category><category domain="type">advisory</category><category>masquerading</category><category>defense-evasion</category><category>initial-access</category><category>malware</category><category>windows</category></item></channel></rss>