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
Software
Security Apps
Other security for Windows, Mac, Linux
Harmony Endpoint by Check Point
Message
<blockquote data-quote="Trident" data-source="post: 1048574" data-attributes="member: 99014"><p>One of the detections (gen.win.processhollowing) seems to be a generic detection for code injection via process hollowing (run process -> pause process -> replace portion of process memory with malicious code -> resume process). Seeing a process hollowing detection by behavioural blocking is quite unusual, many AVs are totally blind to that. Some can catch initial scripts early by using local emulator in memory but the emulator doesn’t have all day, it’s only got milliseconds and by using a JS with useless math operations and malicious actions somewhere in the middle, local emulator can easily be bypassed (unlike full blown emulation in the cloud that has the time).</p><p></p><p>This is why it has become attackers favourite. Quite a lot of malware can be blocked by this detection.</p><p></p><p>So when Check Point was saying that fileless malware is not a problem for behavioural guard, they’ve not been joking.</p><p>[URL unfurl="true"]https://blog.checkpoint.com/security/file-less-malware-no-match-for-sandblast-agent/amp/[/URL]</p></blockquote><p></p>
[QUOTE="Trident, post: 1048574, member: 99014"] One of the detections (gen.win.processhollowing) seems to be a generic detection for code injection via process hollowing (run process -> pause process -> replace portion of process memory with malicious code -> resume process). Seeing a process hollowing detection by behavioural blocking is quite unusual, many AVs are totally blind to that. Some can catch initial scripts early by using local emulator in memory but the emulator doesn’t have all day, it’s only got milliseconds and by using a JS with useless math operations and malicious actions somewhere in the middle, local emulator can easily be bypassed (unlike full blown emulation in the cloud that has the time). This is why it has become attackers favourite. Quite a lot of malware can be blocked by this detection. So when Check Point was saying that fileless malware is not a problem for behavioural guard, they’ve not been joking. [URL unfurl="true"]https://blog.checkpoint.com/security/file-less-malware-no-match-for-sandblast-agent/amp/[/URL] [/QUOTE]
Insert quotes…
Verification
Post reply
Top