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
Malware Analysis
"pyrate", Behavior Blocker Bypass POC #3
Message
<blockquote data-quote="MacDefender" data-source="post: 881353" data-attributes="member: 83059"><p>I am in agreement. I do not believe signature detection is the right thing to do, and I'm kind of surprised that this one wasn't marked as a "hoax" like my last few.</p><p></p><p>BTW, the signature for this file is very specific. This change alone (from single quotes to 3 quotes) results in no detection:</p><p>[code]</p><p>- encrypt(dir+filename, dir+filename+""".enc""")</p><p>+ encrypt(dir+filename, dir+filename+".enc")</p><p>[/code]</p><p></p><p></p><p>In my opinion it's almost a waste of time for ESET to be adding signatures for this script. Signature detections are not the right approach here. Maybe a Python sandbox or better, runtime behavior detection.</p><p></p><p></p><p>EDIT: What I would really like is an explanation for why their Ransomware Shield isn't working against this sample. ESET says <a href="https://help.eset.com/glossary/en-US/technology_ransomware_protection.html" target="_blank">Ransomware Shield | ESET Glossary | ESET Online Help</a></p><p></p><p></p><p>This sounds like a behavior blocker and similar to how WiseVector stops ALL variants of this attack, and how KSW and some other behavior blockers can stop the start.bat variant.</p></blockquote><p></p>
[QUOTE="MacDefender, post: 881353, member: 83059"] I am in agreement. I do not believe signature detection is the right thing to do, and I'm kind of surprised that this one wasn't marked as a "hoax" like my last few. BTW, the signature for this file is very specific. This change alone (from single quotes to 3 quotes) results in no detection: [code] - encrypt(dir+filename, dir+filename+""".enc""") + encrypt(dir+filename, dir+filename+".enc") [/code] In my opinion it's almost a waste of time for ESET to be adding signatures for this script. Signature detections are not the right approach here. Maybe a Python sandbox or better, runtime behavior detection. EDIT: What I would really like is an explanation for why their Ransomware Shield isn't working against this sample. ESET says [URL="https://help.eset.com/glossary/en-US/technology_ransomware_protection.html"]Ransomware Shield | ESET Glossary | ESET Online Help[/URL] This sounds like a behavior blocker and similar to how WiseVector stops ALL variants of this attack, and how KSW and some other behavior blockers can stop the start.bat variant. [/QUOTE]
Insert quotes…
Verification
Post reply
Top