What is the XProtect process, and why is it using CPU on my Mac?
Last reviewed: 19 November 2026. Path, bundle, launchd jobs and scan schedule checked on macOS 26.3.1.
The process named XProtect is the background scanner of Apple's built-in malware protection, which looks for and removes known malware. launchd starts it on a schedule and at startup, so it appears for a while, uses CPU and disk, then exits. It is part of macOS and the activity is expected.
XProtect at a glance
| XProtect | |
|---|---|
| Made by | Apple (part of macOS, XProtect) |
| Type | Background scanner (runs as a daemon and as a per-user agent) |
| Location | /Library/Apple/System/Library/CoreServices/XProtect.app/Contents/MacOS/XProtect |
| Runs as | root for the system scan, plus a copy as your user for the user scan |
| Started by | launchd job com.apple.XProtect.daemon.scan |
| Bundle ID | com.apple.XProtectFramework.XProtect |
| Can you quit it? | Yes, but the scan simply runs again at its next scheduled time. |
What is XProtect?
XProtect is Apple's built-in antivirus technology. Apple's Platform Security guide says it includes technology to remediate infections and "continues to periodically check for infections". The XProtect process is that periodic check. Its app bundle lives in /Library/Apple/System/Library/CoreServices/XProtect.app, which Apple updates separately from macOS, and on this Mac it contains modules named XProtectRemediator followed by a malware family name, such as Adload or Pirrit.
launchd starts it from several jobs in /Library/Apple/System/Library/LaunchDaemons and LaunchAgents: a scan at startup (com.apple.XProtect.daemon.scan.startup) and repeating scans as root and as your user (com.apple.XProtect.daemon.scan and com.apple.XProtect.agent.scan). On this Mac the repeating jobs ask for a fast scan every 6 hours, a fuller scan daily and a slow scan weekly; only the fast scan is allowed to run on battery power.
Is XProtect safe?
Yes. It is signed by Apple with the identifier com.apple.XProtectFramework.XProtect and lives under /Library/Apple, the folder Apple uses for components it updates in the background. It is part of the protection Apple describes, not malware.
Why does XProtect use so much CPU, disk and memory?
- A scheduled scan. The launchd jobs mark the scans as CPU intensive and disk intensive. macOS runs them at utility priority, so the scan slows down rather than blocking your work.
- Startup. A separate job runs a scan when the Mac starts, so XProtect often appears shortly after a restart or login.
- Reading files to check them. Scanning means reading the locations where known malware installs itself, which shows as disk reads while the scan runs.
- Memory released when it finishes. The jobs set
EnablePressuredExit, which lets macOS end XProtect once it is idle. On this Mac launchd recorded its last exit reason as an idle exit, so it does not linger in memory after a scan.
How much CPU is normal for XProtect?
XProtect appearing for a few minutes with noticeable CPU and disk use, then disappearing, is normal. Expect it after startup and every few hours.
When it is not scanning it is not running at all, so seeing no XProtect process is also normal.
How do you stop XProtect from using so much CPU?
- Let the scan finish. The scan ends on its own. Leaving the Mac connected to power helps, because the daily and weekly scans are set not to run on battery.
- Check the installed version. In Terminal, run
xprotect versionto see the version of the XProtect data on the Mac andxprotect checkto see what is available online. - Keep security responses turned on. In System Settings > General > Software Update, open the Automatic Updates options and keep Install Security Responses and system files on so the scanner has current rules.
- See what it did. Run
xprotect logsin Terminal to review recent XProtect activity.
When should you worry about XProtect?
If XProtect stays at high CPU for an hour or more on every run, note the time and check its logs. It is not expected to run continuously.
If macOS tells you it removed or blocked malware, the scanner did its job. Change passwords you may have typed into anything suspicious that you installed.
How do you check XProtect in Activity Monitor and Terminal?
Open Activity Monitor (Applications > Utilities), choose View > All Processes, and type XProtect in the search field. The CPU tab shows its % CPU. The Disk tab shows its Bytes Written and Bytes Read. 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 XProtect process with its PID, user, CPU and memory (RSS is resident memory in kilobytes). fs_usage prints each file it reads or writes until you press Control-C; it needs an administrator password.
ps -axo pid,user,%cpu,%mem,rss,command | grep -F 'XProtect' | grep -v grep
sudo fs_usage -w -f filesys XProtect
How can Thrum help with XProtect?
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 XProtect 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 XProtect
Is XProtect a virus?
No. It is Apple's malware scanner, signed by Apple and stored in /Library/Apple/System/Library/CoreServices.
How often does XProtect scan?
On macOS 26.3.1 its launchd jobs request a fast scan every 6 hours, a daily scan and a weekly scan, plus one at startup. macOS decides the exact time based on power and activity.
What is the difference between XProtect, xprotectd and XprotectService?
XProtect is the scheduled scanner app, xprotectd is the daemon that checks apps as they are launched, and XprotectService is an analysis service inside the XprotectFramework.
Sources
- xprotect(1) man page: run man xprotect in Terminal
- Apple Platform Security: Protecting against malware in macOS