How to clean a Mac from a rootkit that hides in the kernel extensions
A kernel-level rootkit can use a legacy kernel extension, modern system extension, or privileged helper to hide its files and processes. Deleting the visible app may leave persistence behind, so the Mac should be treated as untrusted until its operating system is rebuilt and checked from a clean device.
The method depends on the macOS release and whether the Mac uses Intel or Apple silicon. Recent systems restrict third-party kexts, yet trojanised installers can abuse signed components, login items, scripts, and configuration profiles. Slowdowns, disappearing files, changed accounts, disabled security tools, or unexplained traffic are signals to investigate, not proof on their own.
Disconnect Wi-Fi and Ethernet before testing anything, and use another trusted device for banking, email, work, and password resets. This matters in Australia, where one Mac often handles online banking, superannuation, Centrelink or Medicare information, and a work VPN; using public café Wi-Fi in Sydney, Melbourne, or Brisbane to hunt for a cleaner would add avoidable exposure.
Preserve irreplaceable documents and photos before making changes, and keep the original disk untouched if an investigation may be needed. If an Australian organisation handled affected personal information, the Privacy Act 1988 and the Notifiable Data Breaches scheme may require an assessment. The Australian Cyber Security Centre and Scamwatch provide authoritative security and scam guidance, while an established local computer-repair business is a safer source for a second opinion than an unknown rootkit-remover download.
| Approach |
What it can establish |
Main limitation |
| Built-in settings review |
Shows enabled agents, profiles, and applications |
A rootkit may conceal its own entries |
systemextensionsctl list |
Identifies installed system extensions and publishers |
It is an inventory, not proof of a clean system |
| Reputable macOS scanner |
Can find some unwanted components and persistence |
No scan proves a compromised kernel is safe |
| Full macOS reinstall |
Replaces the old operating-system environment |
Requires verified backups and may need specialist work |
Recognise the signs and establish the scope
Open System Settings and review Login Items & Extensions, installed applications, browser helpers, profiles, and network tools. systemextensionsctl list can inventory system extensions on current releases, while older Macs may expose legacy kext details through kextstat or a similar command. Compare names, dates, and publishers with your own records; a rootkit can falsify even this output.
Also check for unexpected administrator accounts, constant security prompts, altered DNS or proxy settings, and a Mac that remains active when it should be idle. If clipboard contents, typed text, or credentials may also be exposed, the separate guide to identifying a hidden keylogger offers useful checks, but it does not diagnose a rootkit. Use a known-clean computer to change important passwords, and do not enter credentials into the suspect Mac.
Isolate the Mac and preserve useful data
Leave the Mac powered only if an incident-response professional specifically needs its memory state; otherwise shut it down after disconnecting the network. Unplug external drives and shared folders. Do not install a cleaner from an unverified source, and do not run sudo commands copied from a forum post; either action can destroy evidence or give malware another chance to execute.
Copy documents, photographs, and records to an encrypted drive or trusted cloud account, excluding applications, disk images, and extension bundles. If files are also encrypted, the recover files after ransomware workflow explains how to assess recoverable copies without touching the original evidence. Confirm that a backup opens on another computer, and record symptoms, installation dates, and messages that may have delivered the suspect software.
Inspect extensions and launch items
Legacy .kext bundles commonly sit in /Library/Extensions or /System/Library/Extensions; modern system extensions and drivers are managed differently. A legitimate file can still be altered, and a malicious component can live outside those folders. On Apple silicon, do not approve an unfamiliar legacy extension merely to test it, and never lower security settings for convenience.
With the Mac still offline, review login items, background items, device-management profiles, and systemextensionsctl list. Inspect /Library/LaunchAgents, /Library/LaunchDaemons, and the user LaunchAgents folder for unexpected files, then compare signing information and dates. Remove unwanted software through its official uninstaller or macOS controls. Do not double-click suspicious bundles; record their paths and identifiers for analysis, and avoid deleting unfamiliar entries solely by name.
Remove the compromise and rebuild trust
For a confirmed kernel-level compromise, removing one extension is rarely a dependable fix. Reinstall macOS from Apple’s official Recovery or installation media: on an Intel Mac, hold Command-R at startup; on Apple silicon, hold the power button until startup options appear. Restore only selected user data and change passwords from a different device. If persistence survives a complete erase, have the drive, firmware, and hardware examined by a qualified specialist rather than returning the Mac to service.
Before erasing, keep an offline copy of anything irreplaceable. In a related ransomware incident, the restore files with EaseUS guide can help explain recovery options, but work on a duplicate volume, never the only copy; obtain the tool from its official site, not a ransom-message link. After reinstalling, restore preferences selectively, install only current signed applications, and confirm FileVault, the firewall, Gatekeeper, and security updates are active.
Reduce reinfection and protect Australian users
Keep macOS and applications patched, enable automatic updates and FileVault, and require multifactor authentication for banking, email, and work accounts. Install extensions only from a vendor’s official site, and review Login Items & Extensions after software updates or remote-support sessions. Because one-time codes can be intercepted, reset them from a clean device.
Public Wi-Fi in Sydney, Melbourne, Brisbane, or regional towns is convenient, but it is not a safe place to repair a compromised computer. Use a trusted home connection or private hotspot for updates and account recovery, and choose established Australian retailers or service providers with clear privacy policies. Keep two or more backups, including one offline, test a sample restore, and consult the ACSC or Scamwatch when a message impersonates a courier, bank, or software vendor.
A Mac that hosted a kernel-level rootkit should be considered clean only after a trusted reinstall and selective restore stop the symptoms, persistence points have been reviewed, and accounts have been secured elsewhere. That sequence provides a defensible recovery rather than a cosmetic cleanup.