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
Guides - Privacy & Security Tips
Windows processes which are significantly important
Message
<blockquote data-quote="Deleted member 65228" data-source="post: 689246"><p>I am not sure why, I was thinking this too when I read this thread today. I know you can enable it as a protected process on modern versions of Windows... Maybe it isn't protected by default because it is harder to abuse by default (for example it is under SYSTEM therefore without a zero-day RCE exploit you cannot inject code into it unless you're elevated and have debugging rights anyway). And malware with admin rights doesn't need to care for lsass.exe, it can do other things. That could be the reason why...</p><p></p><p>Csrss.exe is a protected process now though and same circumstance as the above, interesting.</p><p></p><p>You can reverse csrss.exe, lsass.exe and their exclusive modules in IDA to learn more about it. You can get the debugging symbols (IDA should do it automatically by connecting and retrieving for you) so you'll be able to see the function names properly and the such. <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite109" alt=":)" title="Smile :)" loading="lazy" data-shortname=":)" /></p></blockquote><p></p>
[QUOTE="Deleted member 65228, post: 689246"] I am not sure why, I was thinking this too when I read this thread today. I know you can enable it as a protected process on modern versions of Windows... Maybe it isn't protected by default because it is harder to abuse by default (for example it is under SYSTEM therefore without a zero-day RCE exploit you cannot inject code into it unless you're elevated and have debugging rights anyway). And malware with admin rights doesn't need to care for lsass.exe, it can do other things. That could be the reason why... Csrss.exe is a protected process now though and same circumstance as the above, interesting. You can reverse csrss.exe, lsass.exe and their exclusive modules in IDA to learn more about it. You can get the debugging symbols (IDA should do it automatically by connecting and retrieving for you) so you'll be able to see the function names properly and the such. :) [/QUOTE]
Insert quotes…
Verification
Post reply
Top