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
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
Microsoft Defender
How to prevent efficiently Defender from considering a given VBS script as containing a threat
Message
<blockquote data-quote="Andy Ful" data-source="post: 934935" data-attributes="member: 32260"><p>That is the part I am not sure of. That is why I wrote that such files can be specially whitelisted by the AV vendor (standard submission may fail). For example, I submitted one of my executables to Emsisoft and Bitdefender. The executable is whitelisted, so it can be run. But still, some actions are blocked by the Emsisoft behavior blocker and by BitDefender ATP. It seems that in some cases the AV vendor does not want to whitelist globally (for all users) the file and all its actions, but allows the user to exclude unwanted blocks locally.</p><p>That is why I am curious what decision will be made by Microsoft in the case of this particular script.</p><p></p><p>Edit.</p><p>The term "AMSI detections" can be misguiding, because AMSI is a monitoring feature (does not detect malicious behavior). I had in mind the behavior-based blocks that use the AMSI-paired machine models. Malicious scripts blocked by AMSI-paired machine models are reported in Microsoft Defender Security Center as follows:</p><ul> <li data-xf-list-type="ul">Trojan:JS/Mountsi.A!ml</li> <li data-xf-list-type="ul">Trojan:Script/Mountsi.A!ml</li> <li data-xf-list-type="ul">Trojan:O97M/Mountsi.A!ml</li> <li data-xf-list-type="ul">Trojan:VBS/Mountsi.A!ml</li> <li data-xf-list-type="ul">Trojan: PowerShell/Mountsi.A!ml</li> </ul></blockquote><p></p>
[QUOTE="Andy Ful, post: 934935, member: 32260"] That is the part I am not sure of. That is why I wrote that such files can be specially whitelisted by the AV vendor (standard submission may fail). For example, I submitted one of my executables to Emsisoft and Bitdefender. The executable is whitelisted, so it can be run. But still, some actions are blocked by the Emsisoft behavior blocker and by BitDefender ATP. It seems that in some cases the AV vendor does not want to whitelist globally (for all users) the file and all its actions, but allows the user to exclude unwanted blocks locally. That is why I am curious what decision will be made by Microsoft in the case of this particular script. Edit. The term "AMSI detections" can be misguiding, because AMSI is a monitoring feature (does not detect malicious behavior). I had in mind the behavior-based blocks that use the AMSI-paired machine models. Malicious scripts blocked by AMSI-paired machine models are reported in Microsoft Defender Security Center as follows: [LIST] [*]Trojan:JS/Mountsi.A!ml [*]Trojan:Script/Mountsi.A!ml [*]Trojan:O97M/Mountsi.A!ml [*]Trojan:VBS/Mountsi.A!ml [*]Trojan: PowerShell/Mountsi.A!ml [/LIST] [/QUOTE]
Insert quotes…
Verification
Post reply
Top