The first step to get a handle on SVCHost is to recognize what is ‘normal’. SVCHost is nothing more than a service the runs other services. You can internet search to get more info, but that’s essential to what it does. It is a fundamental core component of Windows. So IF Windows is assumed to be clean, then one can assume that SVCHost is also clean. Given the two foregoing premise, then whatever SVCHost does should be normal behvior.
What I’ve done is open notepad and paste the following:
Tasklist /FI “IMAGENAME eq svchost.exe” /svc
pause
I saved that file as Process_Tool.cmd. Then I created a shortcut on my desktop linking to that file. When you click the shortcut it will open up a DOS window and dsiplay all the services that are running under SVCHost. You need to get familiiar with what is normal. IF there’s an unual entry that ever shows up, or a process w/no name, that’s a good sign that SVCHost has been hijacked. Other than that what do you care? As long as it doesn’t have anything odd in its service process list, its assumbed to be legit Microsoft business.
On my system the following zones are allowed connection by SVCHost:
Akamai - SVCHost
Akamai - ARM/SVCHost - 80/443
AkamaiTech - SVCHost - 80 / 443
Akamai - ARM / SVCHost - 443
AkamaiTech - SVCHost - 443
*Akamai FT - SVCHost
eurorings.net - SVCHost
*GBLX - SVCHost
*GBLX - SVChost / ARM - 443
*Hurricane - SVCHost
*Level 3 - SVCHost
llnw.net - SVCHost
msecn.net - CIS / SVCHost / HelpCtr / VS
msecn - 80 / 443
msecn.net - 443
*MS 1BLK - SVCHost 80/443
*MS 1BLK - SVCHost - 443
*MS-Global-Net - SVCHost - 80/443
*NTT America - AcroRd32 / SVCHost
*NTT America - SVCHost
PCCWGlobal.net - CIS / jaucheck / SVCHost
qwest.net - jaucheck / SVCHost
qwest.net - SVCHost
*Qwest / Akamai - CIS / SVCHost
The key to the zone names is:
- designates unpublished domain (non-transferable IP owner - owner is component of internet backbone) - otherwise the zone name is the domain name
between hypens: applications using the zone name
number suffix: ports used by specific zone name (if none port 80 is default)
Network zones are sorted alphabetically by domain name / application / port
Zones may end up beging shared between applications, so when an IP address is discovered to already exist in some zone, the zone is either renamed (to include the new app name) and the existing ren-named zone added to the new app, or the particular IP pulled out of the existing zone, and a new zone created and that IP put into the new zone. That usually becomes an issue when a zone that is default port 80 suddenly is discovered to share port 80 & 443. In that case I make a new zone and suffix it with 80/443, and create a new rule allowing access to both port 80 & 443 for that zone. The pre-existing rules remain unaltered and are by default all connecting to port 80.
The * prefix zones are all referencing the unassignable IP address owner netname CIDR mask. For example:
*GBLX = Global Crossing In any *GBLX zone will be only the specific IP addresses that any arbitrary application connects to. However, I have a zone called:
_ARIN (IP Owner): Global Crossing
64.208.0.0/255.255.0.0
64.209.0.0/255.255.128.0
64.211.0.0/255.255.128.0
64.211.128.0/255.255.192.0
64.211.192.0/255.255.224.0
64.212.0.0/255.252.0.0
206.57.0.0/255.255.128.0
206.132.0.0/255.255.128.0
208.48.224.0/255.255.0.0
208.49.0.0/255.255.224.0
208.50.0.0/255.255.0.0
208.50.192.0/255.255.192.0
208.51.0.0/255.255.0.0
For any IP address that fits into the network range of those subnet masks, I put it into the proper * zone (or create as needed). If I can’t find it in there, then I have to look it up. I either find a new IP Owner, or have to add to the existing network subnets.