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
ConfigureDefender utility for Windows 10/11
Message
<blockquote data-quote="Andy Ful" data-source="post: 926176" data-attributes="member: 32260"><p>The malware was not a standalone installer, but an archive with a portable IObit License Manager program - one DLL was replaced by malicious unsigned DLL. This DLL dropped DeroHE ransomware to C:\Program Files (x86)\IObit\iobit.dll . This malware was also uploaded to VS via Iobit.rar (packed iobit.dll):</p><p></p><p>[ATTACH=full]253159[/ATTACH]</p><p></p><p><a href="https://www.virustotal.com/gui/file/5fdf24f6aef41386e82248426859b6cf9fe26691c42a42a6085d88300591e36f/detection" target="_blank">VirusTotal</a></p><p></p><p>So, it was probably detected by WD very quickly. The detection is <strong><span style="color: rgb(184, 49, 47)">Program:Win32/Wacapew.C!ml </span></strong>which is (pre-execution) behavior-based detection. The actual signature detection of iobit.dll is Ransom:Win32/Vigorf.A</p><p></p><p>When this ZIP archive is unpacked with a built-in Windows unpacker, the malicious DLL gets MOTW. So it is checked by WD "Block AT First Sight" after being unpacked. This will prevent the infection of all WD users except maybe the first victim (WD user). Of course, the malicious DLL could be possibly detected by WD behavior-based ML in the cloud, especially with ConfigureDefender HIGH preset.</p><p></p><p>The malware could be also mitigated by several WD advanced settings. For example, adding exclusions to Windows Defender could be prevented in this particular malware example by the ASR rule <s>"Block process creations originating from PSExec and WMI commands"</s> <strong>"</strong>Block executable files from running unless they meet a prevalence, age, or trusted list criteria<strong>" </strong>which is present in ConfigureDefender MAX preset.</p><p></p><p><strong>Anyway, the delivery method is so convincing (trusted IOBIT forum) that in most cases the users simply turn off the protection and install the malware. So, the problem here is not the AV protection but human imperfection.</strong></p><p></p><p>A good solution for such threats was already presented on MT:</p><p><strong><a href="https://malwaretips.com/threads/windows-defender-delay-protection.101566/" target="_blank">Q&A - Windows Defender Delay Protection. | MalwareTips Community</a></strong></p><p><strong></strong></p><p><strong>Edit1.</strong></p><p>The malware uses rundll32.exe to run iobit.dll and this behavior is blocked by the ASR rule <strong>"</strong>Block executable files from running unless they meet a prevalence, age, or trusted list criteria<strong>".</strong></p><p><strong></strong></p><p><strong>Edit2.</strong></p><p>From the posts made by malware victims, it follows that it could bypass the protection of most AVs (including WD and Kaspersky). But, from the picture above it also follows that these two AVs detected the malware very quickly after the attack.</p><p>The users who use 7-Zip or a similar unpacker that does not preserve MOTW, could not be protected very quickly by Windows Defender (default settings) because the Block At First Sight feature was not triggered for the malicious DLL in the IObit License Manager package.</p></blockquote><p></p>
[QUOTE="Andy Ful, post: 926176, member: 32260"] The malware was not a standalone installer, but an archive with a portable IObit License Manager program - one DLL was replaced by malicious unsigned DLL. This DLL dropped DeroHE ransomware to C:\Program Files (x86)\IObit\iobit.dll . This malware was also uploaded to VS via Iobit.rar (packed iobit.dll): [ATTACH type="full" alt="1611091876174.png"]253159[/ATTACH] [URL='https://www.virustotal.com/gui/file/5fdf24f6aef41386e82248426859b6cf9fe26691c42a42a6085d88300591e36f/detection']VirusTotal[/URL] So, it was probably detected by WD very quickly. The detection is [B][COLOR=rgb(184, 49, 47)]Program:Win32/Wacapew.C!ml [/COLOR][/B]which is (pre-execution) behavior-based detection. The actual signature detection of iobit.dll is Ransom:Win32/Vigorf.A When this ZIP archive is unpacked with a built-in Windows unpacker, the malicious DLL gets MOTW. So it is checked by WD "Block AT First Sight" after being unpacked. This will prevent the infection of all WD users except maybe the first victim (WD user). Of course, the malicious DLL could be possibly detected by WD behavior-based ML in the cloud, especially with ConfigureDefender HIGH preset. The malware could be also mitigated by several WD advanced settings. For example, adding exclusions to Windows Defender could be prevented in this particular malware example by the ASR rule [S]"Block process creations originating from PSExec and WMI commands"[/S] [B]"[/B]Block executable files from running unless they meet a prevalence, age, or trusted list criteria[B]" [/B]which is present in ConfigureDefender MAX preset. [B]Anyway, the delivery method is so convincing (trusted IOBIT forum) that in most cases the users simply turn off the protection and install the malware. So, the problem here is not the AV protection but human imperfection.[/B] A good solution for such threats was already presented on MT: [B][URL='https://malwaretips.com/threads/windows-defender-delay-protection.101566/']Q&A - Windows Defender Delay Protection. | MalwareTips Community[/URL] Edit1.[/B] The malware uses rundll32.exe to run iobit.dll and this behavior is blocked by the ASR rule [B]"[/B]Block executable files from running unless they meet a prevalence, age, or trusted list criteria[B]". Edit2.[/B] From the posts made by malware victims, it follows that it could bypass the protection of most AVs (including WD and Kaspersky). But, from the picture above it also follows that these two AVs detected the malware very quickly after the attack. The users who use 7-Zip or a similar unpacker that does not preserve MOTW, could not be protected very quickly by Windows Defender (default settings) because the Block At First Sight feature was not triggered for the malicious DLL in the IObit License Manager package. [/QUOTE]
Insert quotes…
Verification
Post reply
Top
