Forums
New posts
Search forums
News
Security News
Technology News
Giveaways
Giveaways, Promotions and Contests
Discounts & Deals
Reviews
Users Reviews
Video Reviews
Support
Windows Malware Removal Help & Support
Inactive Support Threads
Mac Malware Removal Help & Support
Mobile Malware Removal Help & Support
Blog
Log in
Register
What's new
Search
Search titles only
By:
Search titles only
By:
Reply to thread
Menu
Install the app
Install
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Forums
Software
Security Apps
Hard_Configurator Tools
Simple Windows Hardening
Message
<blockquote data-quote="Andy Ful" data-source="post: 989778" data-attributes="member: 32260"><p><strong><span style="font-size: 18px">SWH vs. TA551 phishing campaigns</span></strong></p><p><span style="font-size: 12px">[URL unfurl="true"]https://redcanary.com/threat-detection-report/threats/ta551/[/URL]</span></p><p></p><p><span style="font-size: 15px">[ATTACH=full]266827[/ATTACH]</span></p><p></p><p>The report shows that password-protected ZIP attachments with Word documents were used in the attacks. This pretty common type of attack is blocked by default in SWH via disabling VBA in MS Office.</p><p></p><p>Such attacks can be easily prevented even without SWH, by not allowing macros in MS Office documents. If macros are enabled then the defense is more complicated. But in most cases, the attacks can be mitigated by:</p><ol> <li data-xf-list-type="ol">Restricting network connections of MS Word and popular LOLBins (certutil.exe, mshta.exe, etc.). One can use the FirewallHardening tool for that (or apply manually the rules in the firewall).<br /> But, this attack can be modified to drop the payload embedded/encoded in the document - in such a case, restricting network connection will not help.</li> <li data-xf-list-type="ol">Applying parent-child protection to prevent spawning by MS Word some LOLBins (regsvr32.exe, rundll32.exe, etc.) that can execute DLLs. This can be done via the HIPS module in AV or ASR rules (like in Microsoft Defender / ConfigureDefender HIGH settings). But, the macro in the attack can be modified by accessing the WMI service via <em>WinMgmts moniker</em> to bypass the parent-child monitoring. So, one has to additionally restrict WMI (can be done in Microsoft Defender via ASR rules).</li> </ol><p>It is worth knowing that this type of attack does not use *.exe payloads. The final payload (Ursnif, Zloader, Valak, IceId, Qbot) was injected into the system process (svchost.exe, msiexec.exe, etc.). Such injections are not easy to detect by Avs.</p><p></p><p>Edit.</p><p>Another example of the recent TA551 attack via ISO file (LNK + DLL) was analyzed here:</p><p>[URL unfurl="false"]https://malwaretips.com/threads/simple-windows-hardening.102265/post-985951[/URL]</p></blockquote><p></p>
[QUOTE="Andy Ful, post: 989778, member: 32260"] [B][SIZE=5]SWH vs. TA551 phishing campaigns[/SIZE][/B] [SIZE=3][URL unfurl="true"]https://redcanary.com/threat-detection-report/threats/ta551/[/URL][/SIZE] [SIZE=4][ATTACH type="full" alt="1653297663480.png"]266827[/ATTACH][/SIZE] The report shows that password-protected ZIP attachments with Word documents were used in the attacks. This pretty common type of attack is blocked by default in SWH via disabling VBA in MS Office. Such attacks can be easily prevented even without SWH, by not allowing macros in MS Office documents. If macros are enabled then the defense is more complicated. But in most cases, the attacks can be mitigated by: [LIST=1] [*]Restricting network connections of MS Word and popular LOLBins (certutil.exe, mshta.exe, etc.). One can use the FirewallHardening tool for that (or apply manually the rules in the firewall). But, this attack can be modified to drop the payload embedded/encoded in the document - in such a case, restricting network connection will not help. [*]Applying parent-child protection to prevent spawning by MS Word some LOLBins (regsvr32.exe, rundll32.exe, etc.) that can execute DLLs. This can be done via the HIPS module in AV or ASR rules (like in Microsoft Defender / ConfigureDefender HIGH settings). But, the macro in the attack can be modified by accessing the WMI service via [I]WinMgmts moniker[/I] to bypass the parent-child monitoring. So, one has to additionally restrict WMI (can be done in Microsoft Defender via ASR rules). [/LIST] It is worth knowing that this type of attack does not use *.exe payloads. The final payload (Ursnif, Zloader, Valak, IceId, Qbot) was injected into the system process (svchost.exe, msiexec.exe, etc.). Such injections are not easy to detect by Avs. Edit. Another example of the recent TA551 attack via ISO file (LNK + DLL) was analyzed here: [URL unfurl="false"]https://malwaretips.com/threads/simple-windows-hardening.102265/post-985951[/URL] [/QUOTE]
Insert quotes…
Verification
Post reply
Top
