What is XprotectService, and why is it using CPU on my Mac?
Last reviewed: 19 November 2026. Path, account and code signature checked on macOS 26.3.1.
XprotectService is an XPC service inside Apple's XprotectFramework, the framework behind XProtect, the malware checks built into macOS. Its code signature names it the XProtect analysis service, and it uses CPU while files are being checked. It is part of macOS and safe to leave running.
XprotectService at a glance
| XprotectService | |
|---|---|
| Made by | Apple (part of macOS, XProtect) |
| Type | XPC service |
| Location | /System/Library/PrivateFrameworks/XprotectFramework.framework/Versions/A/XPCServices/XprotectService.xpc/Contents/MacOS/XprotectService |
| Runs as | root |
| Can you quit it? | Not usefully. macOS starts it again when XProtect needs it. |
What is XprotectService?
An XPC service is a small helper program that macOS starts on demand for another component. XprotectService is bundled inside XprotectFramework.framework in /System/Library/PrivateFrameworks, and its code signature identifier is com.apple.XprotectFramework.AnalysisService. Apple does not publish more detail about it, but its location and name tie it to XProtect, which checks apps for known malware at first launch, after they change, and after signatures update.
Unlike most daemons it has no launchd property list of its own; it is started as a service of the framework when another XProtect component needs it, and runs as root.
Is XprotectService safe?
Yes. It is on the read-only system volume inside an Apple framework and is signed by Apple. You can confirm the path with the ps command below.
Why does XprotectService use so much CPU and memory?
- Checking new or changed apps. Opening apps for the first time and installing updates trigger XProtect checks, which is when this analysis service does its work.
- New XProtect signatures. When Apple ships new XProtect data, macOS checks again with the new rules, which can wake the service.
- Rules held in memory. Holding malware rules while analysing files uses some memory. A few tens of megabytes was observed on this Mac.
How much CPU is normal for XprotectService?
Short bursts of CPU when apps are installed, updated or opened for the first time, and 0% otherwise. It may not be running at all when nothing needs checking.
How do you stop XprotectService from using so much CPU?
- Wait for installs to finish. If you just installed or updated several apps, let the checks complete. The service goes idle on its own.
- Check XProtect's status. Run
xprotect statusin Terminal to confirm XProtect is working normally. - Find what changed. If it keeps waking, look in the Disk tab of Activity Monitor for an app that is constantly writing files, such as a build tool or an updater stuck in a loop.
When should you worry about XprotectService?
Continuous high CPU from XprotectService with no apps being installed or changed is unusual; note the time and look at xprotect logs.
A process with this name outside the XprotectFramework path would not be Apple's.
How do you check XprotectService in Activity Monitor and Terminal?
Open Activity Monitor (Applications > Utilities), choose View > All Processes, and type XprotectService in the search field. The CPU tab shows its % CPU. The Memory tab shows its Memory. Double-click the row for its parent process, memory details and open files.
In Terminal, the first command lists every XprotectService process with its PID, user, CPU and memory (RSS is resident memory in kilobytes).
ps -axo pid,user,%cpu,%mem,rss,command | grep -F 'XprotectService' | grep -v grep
How can Thrum help with XprotectService?
Thrum keeps a live CPU graph in the menu bar. One click shows the eight processes using the most CPU, so you can see when XprotectService is among them and how much it takes. An optional alert tells you when a process stays above a CPU level you choose (50 to 200% of one core) for 1 to 10 minutes. macOS does not let apps quit processes owned by root or other users, so Thrum shows them for information and leaves stopping them to the steps above.
Thrum is $4.99 once with a 14-day free trial and no account. It requires macOS 26 Tahoe on Apple silicon or Intel.
Questions about XprotectService
Why does XprotectService run as root?
It checks software that can be installed anywhere on the Mac, so it runs with system privileges, like the rest of XProtect.
Can I disable XprotectService?
There is no supported way to disable it, and doing so would weaken the malware checks built into macOS.
Sources
- Apple Platform Security: Protecting against malware in macOS
- Code signature: run codesign -dv on the path above in Terminal