<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>FIN7 on Fabrice's Blog</title><link>https://blog.redteamshell.com/tags/fin7/</link><description>Recent content in FIN7 on Fabrice's Blog</description><generator>Hugo</generator><language>en</language><copyright>&lt;a href="https://creativecommons.org/licenses/by-nc/4.0/" target="_blank" rel="noopener">CC BY-NC 4.0&lt;/a></copyright><lastBuildDate>Sun, 07 Sep 2025 13:59:10 -0400</lastBuildDate><atom:link href="https://blog.redteamshell.com/tags/fin7/index.xml" rel="self" type="application/rss+xml"/><item><title>Threat Hunting: FIN7 - Post Compromise Execution</title><link>https://blog.redteamshell.com/posts/2025/09/threat-hunting-fin7-post-compromise-execution/</link><pubDate>Sun, 07 Sep 2025 13:59:10 -0400</pubDate><guid>https://blog.redteamshell.com/posts/2025/09/threat-hunting-fin7-post-compromise-execution/</guid><description>&lt;p>&lt;img src="https://blog.redteamshell.com/images/FIN7_Blog_post2.png" alt="FIN7 - Post Compromise Execution">&lt;/p>
&lt;h3 id="introduction">Introduction&lt;/h3>
&lt;p>In Part 2, we pivot from initial access to what happened next. Using Windows event logs and PowerShell Operational logs in Splunk, we reconstructed FIN7’s execution chain after persistence via a scheduled task, validated key artifacts, and built practical detections you can run.&lt;/p>
&lt;h3 id="what-we-investigated">What we investigated&lt;/h3>
&lt;ul>
&lt;li>Scheduled Task execution timing and payload&lt;/li>
&lt;li>Process tree spawned by the persisted loader&lt;/li>
&lt;li>PowerShell script executions including repeated stagers&lt;/li>
&lt;li>Reconstruction of the staged PowerShell from events (4104) and file hashing for IOC tracking&lt;/li>
&lt;/ul>
&lt;h3 id="interpretation-of-the-decoded-script-from-initial-access-recap">Interpretation of the Decoded Script from Initial Access (Recap)&lt;/h3>
&lt;p>what we have got here is essentially a decoded RTF payload that was obfuscated using &lt;code>\chr&lt;/code> encoding. Once decoded, it reveals a malicious VBScript designed to drop and persist a RAT (remote access trojan). Lets break down the key points :&lt;/p></description></item><item><title>Threat Hunting: FIN7 - Initial Access</title><link>https://blog.redteamshell.com/posts/2025/08/threat-hunting-fin7-initial-access/</link><pubDate>Thu, 14 Aug 2025 19:03:54 -0400</pubDate><guid>https://blog.redteamshell.com/posts/2025/08/threat-hunting-fin7-initial-access/</guid><description>&lt;p>&lt;img src="https://blog.redteamshell.com/images/FIN7_Blog_post1.png" alt="Fin7_blogpost_1">&lt;/p>
&lt;h3 id="introduction">Introduction&lt;/h3>
&lt;p>Welcome to the first post in my Threat Hunting series. We are starting with FIN7’s initial access tradecraft: a phishing-delivered, weaponized RTF that abuses living-off-the-land binaries and scheduled tasks to get a foothold. This post distills the key artifacts and shows practical hunts you can run.&lt;/p>
&lt;blockquote>
&lt;p>This is Part 1 of my Threat Hunting series. Each post focuses on one phase of an intrusion with practical hunts and response tips.&lt;/p></description></item></channel></rss>