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
NoVirusThanks OSArmor
Message
<blockquote data-quote="shmu26" data-source="post: 717837" data-attributes="member: 37647"><p>These command lines parented by svchost are to me the most puzzling of events.</p><p>Most systems have several instances of svchost running simultaneously, so which one did it, and which process was the granddaddy?</p><p></p><p>In process hollowing, it is common for malware to spawn an instance of svchost as a child, and then fill it with malicious code. So you want to rule out the possibility that malware was the granddaddy of the command line.</p><p></p><p>I would check the PID of that particular instance of svchost, and look at the logs to see what else it has done in this system session. Most of the time, you will find that it ran a couple scheduled tasks. If so, this is just another one of those Windows scheduled tasks. </p><p></p><p>That's my take on it, anyways...</p></blockquote><p></p>
[QUOTE="shmu26, post: 717837, member: 37647"] These command lines parented by svchost are to me the most puzzling of events. Most systems have several instances of svchost running simultaneously, so which one did it, and which process was the granddaddy? In process hollowing, it is common for malware to spawn an instance of svchost as a child, and then fill it with malicious code. So you want to rule out the possibility that malware was the granddaddy of the command line. I would check the PID of that particular instance of svchost, and look at the logs to see what else it has done in this system session. Most of the time, you will find that it ran a couple scheduled tasks. If so, this is just another one of those Windows scheduled tasks. That's my take on it, anyways... [/QUOTE]
Insert quotes…
Verification
Post reply
Top