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
Hiding malware in Windows – The basics of code injection
Message
<blockquote data-quote="Eddie Morra" data-source="post: 770183"><p>I haven't looked into that ASR rule yet but I definitely will when I have time to. I have a lot more rules to look into...</p><p></p><p>I was under the impression that ASR only covers scripts (e.g. VBScript, PowerShell (?), Office VBA Macro's). If this is the case, then that ASR rule won't work against Win32-based malware trying to attack lsass.exe for credential theft. I've only ever tested ASR with Office VBA Macro's though, so I do not know the true extent of how far it covers.</p><p></p><p>If you opt-in for the additional Windows 8.1+ lsass.exe protection, you will definitely be covered across everything from Win32-based malware to scripts, etc. though. <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite109" alt=":)" title="Smile :)" loading="lazy" data-shortname=":)" /></p><p></p><p>One thing to note is that with the normal opt-in lsass.exe protection, you aren't going to be notified if an attack is blocked, because the attack will never reach a stage where it is definite that lsass.exe was being attacked for credential theft - so even if you are infected and the credential theft attack is blocked, you may stay unaware of the infection. However, if the attacker falls under the scope of ASR and the ASR rule you mentioned intervenes, you can be notified about the attack attempt by Windows Defender (I've seen Windows Defender notify during testing of my own POCs for the prevention of code injection attacks).</p></blockquote><p></p>
[QUOTE="Eddie Morra, post: 770183"] I haven't looked into that ASR rule yet but I definitely will when I have time to. I have a lot more rules to look into... I was under the impression that ASR only covers scripts (e.g. VBScript, PowerShell (?), Office VBA Macro's). If this is the case, then that ASR rule won't work against Win32-based malware trying to attack lsass.exe for credential theft. I've only ever tested ASR with Office VBA Macro's though, so I do not know the true extent of how far it covers. If you opt-in for the additional Windows 8.1+ lsass.exe protection, you will definitely be covered across everything from Win32-based malware to scripts, etc. though. :) One thing to note is that with the normal opt-in lsass.exe protection, you aren't going to be notified if an attack is blocked, because the attack will never reach a stage where it is definite that lsass.exe was being attacked for credential theft - so even if you are infected and the credential theft attack is blocked, you may stay unaware of the infection. However, if the attacker falls under the scope of ASR and the ASR rule you mentioned intervenes, you can be notified about the attack attempt by Windows Defender (I've seen Windows Defender notify during testing of my own POCs for the prevention of code injection attacks). [/QUOTE]
Insert quotes…
Verification
Post reply
Top