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
Video Reviews - Security and Privacy
G data IS 2018 vs Ransomwares
Message
<blockquote data-quote="cruelsister" data-source="post: 719523" data-attributes="member: 7463"><p>A product just stopping wscript is pointless without detecting and dealing with the underlying vb script that is calling up wscript. If you notice, that vbs script was just using wscript to connect out and download the actual Crab payload and in itself is not the actual ransomware. But as any decent Blackhat will have a duplicate (or similar) script dropped on initial run somewhere on the system and also provide for autostarting or other persistence mechanisms for the daughter. If GD didn't nail it initially one will be getting the same wscript block every time the system is restarted.</p><p></p><p>The pity is that some popular on-demand scanners are also oblivious to this attack mechanism.</p><p></p><p>(ps- if on a Win10 system, nothing should be able to delete/move/quarantine wscript as this resides in the system32 folder. UAC, even at the Off setting, will prevent this. What no doubt actually occurred is that this one specific process was just terminated).</p></blockquote><p></p>
[QUOTE="cruelsister, post: 719523, member: 7463"] A product just stopping wscript is pointless without detecting and dealing with the underlying vb script that is calling up wscript. If you notice, that vbs script was just using wscript to connect out and download the actual Crab payload and in itself is not the actual ransomware. But as any decent Blackhat will have a duplicate (or similar) script dropped on initial run somewhere on the system and also provide for autostarting or other persistence mechanisms for the daughter. If GD didn't nail it initially one will be getting the same wscript block every time the system is restarted. The pity is that some popular on-demand scanners are also oblivious to this attack mechanism. (ps- if on a Win10 system, nothing should be able to delete/move/quarantine wscript as this resides in the system32 folder. UAC, even at the Off setting, will prevent this. What no doubt actually occurred is that this one specific process was just terminated). [/QUOTE]
Insert quotes…
Verification
Post reply
Top