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
Security
General Security Discussions
Any real-time software that uses non-traditional ways to find malware?
Message
<blockquote data-quote="danb" data-source="post: 915218" data-attributes="member: 62850"><p>This is not surprising... the 94 out of 125 files that WV classified as malicious were not filtered or inspected in anyway... I simply counted them as a correct verdict. However, I inspected the files that WV missed to ensure they were 1) valid executables and 2) malicious, and this was after I scanned the malpack for duplicates. This actually works in WV's favor, but I believe it is the only fair way to run the test. So the test was not up to lab standards, but it was pretty close <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite110" alt=";)" title="Wink ;)" loading="lazy" data-shortname=";)" />. But anyway, this would explain why some of the files are not valid executables (and did not execute). Basically, they are files that WV determined to be malicious and I counted them as a correct verdict without inspecting them further.</p><p></p><p>BTW, just curious, are they crashing with or without SBIE?</p></blockquote><p></p>
[QUOTE="danb, post: 915218, member: 62850"] This is not surprising... the 94 out of 125 files that WV classified as malicious were not filtered or inspected in anyway... I simply counted them as a correct verdict. However, I inspected the files that WV missed to ensure they were 1) valid executables and 2) malicious, and this was after I scanned the malpack for duplicates. This actually works in WV's favor, but I believe it is the only fair way to run the test. So the test was not up to lab standards, but it was pretty close ;). But anyway, this would explain why some of the files are not valid executables (and did not execute). Basically, they are files that WV determined to be malicious and I counted them as a correct verdict without inspecting them further. BTW, just curious, are they crashing with or without SBIE? [/QUOTE]
Insert quotes…
Verification
Post reply
Top