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
Security Statistics and Reports
Test of security solutions in blocking attacks on Internet banking
Message
<blockquote data-quote="Adrian Ścibor" data-source="post: 972738" data-attributes="member: 71496"><p>The question should be - why you shouldn't use a non-popular protocol to start attack, insteed know-well HTTP/S by everybody? Imagine a SMB protocol and vulnerability to propagate a huge ransomware attack in 2017 (NotPetya). Why you cannot use diferent attack method than usual? To check protection when it comes to HTTP protocol you can visit our Advanced In The Wild Malware Test on webiste: avlab[.]pl/en/</p><p></p><p>Therefore we want to try different protocol than HTTP/S to check vendor's protection, their reaction on simulate a running malware and delivered to the system in another way.</p><p></p><p></p><p>No, we have used a FTP client to drop malware to the system first. Next, if it wasn't blocked the samples was executed to check for example keylogging protection (system-wide and browser-based) or protection against stealing passwords from files that stored on disk.</p><p></p><p>Dear Readers! If you have another questions to change methodology or add another ways to try bypass protection, you can write here. Next edition of internet banking we can take this into consideration.</p></blockquote><p></p>
[QUOTE="Adrian Ścibor, post: 972738, member: 71496"] The question should be - why you shouldn't use a non-popular protocol to start attack, insteed know-well HTTP/S by everybody? Imagine a SMB protocol and vulnerability to propagate a huge ransomware attack in 2017 (NotPetya). Why you cannot use diferent attack method than usual? To check protection when it comes to HTTP protocol you can visit our Advanced In The Wild Malware Test on webiste: avlab[.]pl/en/ Therefore we want to try different protocol than HTTP/S to check vendor's protection, their reaction on simulate a running malware and delivered to the system in another way. No, we have used a FTP client to drop malware to the system first. Next, if it wasn't blocked the samples was executed to check for example keylogging protection (system-wide and browser-based) or protection against stealing passwords from files that stored on disk. Dear Readers! If you have another questions to change methodology or add another ways to try bypass protection, you can write here. Next edition of internet banking we can take this into consideration. [/QUOTE]
Insert quotes…
Verification
Post reply
Top