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
Hard_Configurator - Windows Hardening Configurator
Message
<blockquote data-quote="Andy Ful" data-source="post: 750764" data-attributes="member: 32260"><p>People on Wilderssecurity forum asked about blocking by Hard_Configurator settings the BAT file located somewhere in the Userspace (XXXX is a UserProfile name):</p><p>[CODE]START "" C:\Users\XXXX\AppData\Local\Temp\knownmalicious.exe[/CODE]</p><p><a href="https://www.wilderssecurity.com/threads/av-comparatives-real-world-protection-test-february-june-2018.406045/page-3#post-2769792" target="_blank">AV-Comparatives: Real-World Protection Test February-June 2018</a></p><p>.</p><p>Of course, it will be blocked, because Hard_Configurator default settings (Recommended SRP) block BAT files (and many others) in the Userspace. So, maybe the more clever SmartScreen bypass would be avoiding BAT files and run the commandline:</p><p>cmd /c START "" C:\Users\XXXX\AppData\Local\Temp\knownmalicious.exe</p><p>or</p><p>PowerShell -command start C:\Users\XXXX\AppData\Local\Temp\knownmalicious.exe</p><p>.</p><p>But then, the executable<strong> knownmalicious.exe </strong>will be blocked too, because Hard_Configurator default settings (Recommended SRP) block EXE files in the Userspace.</p><p>Anyway, the user can run the file <strong>knownmalicious.exe</strong> when using "Run As SmartScreen" via the Explorer right-click menu, but then it will be checked by SmartScreen.</p></blockquote><p></p>
[QUOTE="Andy Ful, post: 750764, member: 32260"] People on Wilderssecurity forum asked about blocking by Hard_Configurator settings the BAT file located somewhere in the Userspace (XXXX is a UserProfile name): [CODE]START "" C:\Users\XXXX\AppData\Local\Temp\knownmalicious.exe[/CODE] [URL='https://www.wilderssecurity.com/threads/av-comparatives-real-world-protection-test-february-june-2018.406045/page-3#post-2769792']AV-Comparatives: Real-World Protection Test February-June 2018[/URL] . Of course, it will be blocked, because Hard_Configurator default settings (Recommended SRP) block BAT files (and many others) in the Userspace. So, maybe the more clever SmartScreen bypass would be avoiding BAT files and run the commandline: cmd /c START "" C:\Users\XXXX\AppData\Local\Temp\knownmalicious.exe or PowerShell -command start C:\Users\XXXX\AppData\Local\Temp\knownmalicious.exe . But then, the executable[B] knownmalicious.exe [/B]will be blocked too, because Hard_Configurator default settings (Recommended SRP) block EXE files in the Userspace. Anyway, the user can run the file [B]knownmalicious.exe[/B] when using "Run As SmartScreen" via the Explorer right-click menu, but then it will be checked by SmartScreen. [/QUOTE]
Insert quotes…
Verification
Post reply
Top
