Noms.exe high CPU usage (what is this process?)

cpu usageprocessservices

I recently discovered process called noms.exe running and maxing out one CPU core on the machine.

I have done all the usual steps trying to collect the information about the process and was surprised by how little I could find out.

So what I know so far:

  1. filename: noms.exe
  2. location: c:\windows\geianoms\noms.exe
  3. company name (as reported by Process Explorer): CBTS (*I have no clue what is this company and what does CBTS stand for. Quick internet search did not give me any clues)
  4. The executable is running as a service. Yet the service name is not descriptive at all, it literally says "noms". The description section of the service is empty (?suspicious?)
  5. It does not seem to be a part of antivirus package. System has McAfee installed and all McAfee executable are easily identifiable.
  6. I seriously doubt that it is an OS component as it is not labeled by Microsoft.
  7. Description in Process Explorer says "NOMS client 64-bit"
  8. Process is permanently stuck in "Wait:UserRequest" state
  9. Working set of the process does not seem to be growing over time
  10. Process consumes 100% of one CPU core
  11. "noms" service is set to manual start in windows services. So it must have been started from somewhere
  12. Search in system registry does not reveal anything except for the actual service record and antivirus + firewall exceptions

Search on the internet for "noms.exe" and "geianoms" keywords did not produce any helpful results except for the fact that someone else has searched for similar/identical file.

Does anyone has any clue what that could be? Any advice would be appreciated.

Best Answer

NOMS stands for Network Object Malware Scanner.

It is product of CBTS and is provided as part of a corporate security system. So the programme is installed on your PC by your corporate IT department.

It is intended to protect the company from dodgy downloads or websites. Which is a different target to the likes of McAfee, which you mention in your question.

The executable was updated a couple of days ago and seems now to use less CPU time, although it still runs at a pretty constant 10%.

The exe is obviously kept protected to stop people like you and I stopping it from running.

Screenshot of EXE Properties