What is xprotectd, and why is it using CPU on my Mac?
Last reviewed: 19 November 2026. Path, account, launchd job, man page and xprotect(1) checked on macOS 26.3.1.
xprotectd is a daemon that belongs to XProtect, the antivirus technology built into macOS that detects and blocks known malware. It is busy when apps are launched for the first time or changed, and when new XProtect signatures arrive. It is part of macOS and should be left running.
xprotectd at a glance
| xprotectd | |
|---|---|
| Made by | Apple (part of macOS, XProtect) |
| Type | System daemon |
| Location | /usr/libexec/xprotectd |
| Runs as | root |
| Started by | launchd job com.apple.security.xprotectd |
| Can you quit it? | Not usefully. launchd starts it again, and malware checks depend on it. |
What is xprotectd?
The man page calls xprotectd "a subsystem of XProtect, a component of MacOS which automatically detects and blocks the execution of known malware." Apple's Platform Security guide says XProtect checks for known malicious content when an app is first launched, when an app has been changed in the file system, and when XProtect signatures are updated.
xprotectd runs as root from the com.apple.security.xprotectd launchd job and works alongside the other XProtect parts: XprotectService, an analysis service inside the XprotectFramework, and the XProtect app that runs scheduled background scans.
Is xprotectd safe?
Yes. It is Apple's malware protection, it lives in /usr/libexec on the read-only system volume, and it is started by launchd. Removing or blocking it would leave the Mac without the built-in malware checks.
Why does xprotectd use so much CPU?
- Apps launched for the first time. New apps are checked against XProtect's signatures before they run, so installing several apps or opening a large one causes a burst.
- Apps that were changed. Apple says XProtect also checks apps that have changed in the file system, so app updates and tools that modify app bundles trigger new checks.
- New signatures. When Apple publishes new XProtect signatures, macOS checks again with the new rules. Apple says these updates arrive independently of macOS updates and are checked for daily by default.
How much CPU is normal for xprotectd?
Near 0% CPU most of the time, with short bursts when apps are opened for the first time or updated. It typically uses only a few megabytes of memory.
How do you stop xprotectd from using so much CPU?
- Check XProtect's status. In Terminal, run
xprotect statusto see XProtect's current state, andxprotect versionto see the version of the installed signatures. - Keep security responses turned on. Open System Settings > General > Software Update, open the Automatic Updates options, and make sure Install Security Responses and system files is on so XProtect keeps receiving new signatures.
- Let installs finish. After installing or updating several apps, give the checks a minute. Activity drops once each new app has been checked.
- Read XProtect's logs. Run
xprotect logsto see recent XProtect activity if you want to know what it checked.
When should you worry about xprotectd?
If macOS shows a message that an item will damage your Mac or contains malware, XProtect has found a match. Let macOS move it to the Trash and do not open it again.
Sustained CPU use with nothing being installed or opened is unusual for xprotectd. Check whether the scheduled XProtect scan (the XProtect process) is running at the same time, which is expected and temporary.
How do you check xprotectd in Activity Monitor and Terminal?
Open Activity Monitor (Applications > Utilities), choose View > All Processes, and type xprotectd in the search field. The CPU tab shows its % CPU. Double-click the row for its parent process, memory details and open files.
In Terminal, the first command lists every xprotectd process with its PID, user, CPU and memory (RSS is resident memory in kilobytes).
ps -axo pid,user,%cpu,%mem,rss,command | grep -F 'xprotectd' | grep -v grep
How can Thrum help with xprotectd?
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 xprotectd 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 xprotectd
Do I need third-party antivirus if xprotectd is running?
Apple describes XProtect as built-in signature-based detection and removal of malware that Apple updates automatically. Whether you add other software is your choice; it is not required for XProtect to work.
How do I update XProtect manually?
Run sudo xprotect update in Terminal. xprotect check shows the version that is available online.
Sources
- xprotectd(8) and xprotect(1) man pages: run man xprotectd in Terminal
- Apple Platform Security: Protecting against malware in macOS