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
Security
Malware Analysis
"pyrate", Behavior Blocker Bypass POC #3
Message
<blockquote data-quote="MacDefender" data-source="post: 880908" data-attributes="member: 83059"><p>Yeah perhaps it would be caught, or enabling of Secure Boot would lead to the malware not executing. But the first reboot after running Windows Setup is into the WinPE installation environment. In there, no antivirus (Windows Defender or otherwise) is allowed to run. Maybe that environment refuses to run files not signed by Microsoft, but I don't think so (third party driver installers can be bundled into there). Either way, it's very risky and sneaky that the payload deployment was intentionally made to happen during a phase of Windows setup where AV isn't running.</p><p></p><p>It's just funny because I have always thought that scanning an external disk before execution is a waste of time since the realtime scanner is going to get around to it anyway. I guess this is one exception to that!</p></blockquote><p></p>
[QUOTE="MacDefender, post: 880908, member: 83059"] Yeah perhaps it would be caught, or enabling of Secure Boot would lead to the malware not executing. But the first reboot after running Windows Setup is into the WinPE installation environment. In there, no antivirus (Windows Defender or otherwise) is allowed to run. Maybe that environment refuses to run files not signed by Microsoft, but I don't think so (third party driver installers can be bundled into there). Either way, it's very risky and sneaky that the payload deployment was intentionally made to happen during a phase of Windows setup where AV isn't running. It's just funny because I have always thought that scanning an external disk before execution is a waste of time since the realtime scanner is going to get around to it anyway. I guess this is one exception to that! [/QUOTE]
Insert quotes…
Verification
Post reply
Top
