Is my Mac hacked?

[theramajor]

The fans on my MPB were spooling up pretty fast so I checked Activity Monitor to see what's going on. I noticed something called 'deleted.' This is what I found:

cwd
/
txt
/System/Library/PrivateFrameworks/CacheDelete.framework/deleted
txt
/Library/Preferences/Logging/.plist-cache.r8vMFLPr
txt
/private/var/db/analyticsd/events.whitelist
txt
/usr/share/icu/icudt64l.dat
txt
/System/Library/MessageTracer/SubmitDiagInfo.default.domains.searchtree
txt
/usr/lib/dyld
0
/dev/null
1
/dev/null
2
/dev/null
3
/System/Library/MessageTracer/SubmitDiagInfo.default.domains.searchtree

 

[Red Menace]

That is just one of thousands of system utilities - what makes you think you are hacked?

 

[2984839]

That's a built-in utility to purge disk caches and nothing to worry about. In the BSD tradition which Apple follows, daemons are processes that run continuously in the background, and their names end with a 'd'. "launchd" is a good example. Thus "deleted" is not the past tense of the English word delete; it's a daemon that performs deletion. It makes more sense if you mentally pronounce it "delete dee". Confusing naming on Apple's part and they should have picked a different term for this daemon.

 

[chabig]

All Macs have that service. It’s normal.

 

[jtstarr]

I just did a search of the process group "com.apple.hiservices-xpcservice (42147)" which brought me to this forum page. I noticed the same high spinup of my MBP fans that theramajor described. Fans spun very fast, but no warm air out the vents; laptop bottom not hot to the touch in the slightest.

Where theramajor had "deleted", I have the aforementioned process group. In my CPU activity monitor, it shows not responding and continues hangup count. We both show the same .dat file, but different associated processes; and different folders: /private/var/db/analyticsd/ vs. /private/var/db/timezone/. Does that seem right? Should I just reboot? I expect it won't occur again....not right away. Suggestions?

cwd
/
txt
/System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/HIServices.framework/Versions/A/XPCServices/com.apple.hiservices-xpcservice.xpc/Contents/MacOS/com.apple.hiservices-xpcservice
txt
/Library/Preferences/Logging/.plist-cache.jT0Zk1Mu
txt
/private/var/db/timezone/tz/2020d.1.0/icutz/icutz44l.dat
txt
/usr/share/icu/icudt64l.dat
txt
/private/var/folders/89/b7ml1pc11lj45w7l66vr8c500000gn/0/com.apple.LaunchServices.dv/com.apple.LaunchServices-1082-v2.csstore
txt
/usr/lib/dyld
0
/dev/null
1
/dev/null
2
/dev/null

 

[tim_fully]

Yeh something not right about this....

cwd
/
txt
/usr/libexec/nsurlsessiond
txt
/Library/Preferences/Logging/.plist-cache.gZicKclg
txt
/usr/share/icu/icudt64l.dat
txt
/private/var/db/analyticsd/events.whitelist
txt
/private/var/db/mds/messages/501/se_SecurityMessages
txt
/usr/lib/dyld
0
/dev/null
1
/dev/null
2
/dev/null

 

[T'hain Esh Kelch]

Apple deamons eating up CPU cycles at random is nothing new.