Detect Launchd in Microsoft Sentinel
Adversaries may abuse the launchd daemon to perform task scheduling for initial or recurring execution of malicious code on macOS. The launchd daemon is responsible for loading and maintaining services within the operating system. It processes property list (plist) files found in /System/Library/LaunchDaemons, /Library/LaunchDaemons (system-wide daemons run as root), /Library/LaunchAgents (user agents run for all users), and ~/Library/LaunchAgents (user agents run for the specific user). Adversaries may install malicious plist files in these directories to achieve persistence, privilege escalation (via LaunchDaemons running as root), or execution at system startup or login. This technique is noted as deprecated by MITRE due to inaccurate original characterization, but the underlying abuse of launchd-controlled directories remains a valid and observed persistence mechanism on macOS.
MITRE ATT&CK
- Canonical reference
- https://attack.mitre.org/techniques/T1053/004/
KQL Detection Query
// Detection for T1053.004 - Launchd abuse on macOS via Microsoft Defender for Endpoint
// Detects plist file creation/modification in LaunchDaemon/LaunchAgent directories
// and suspicious launchctl usage
let LaunchDaemonPaths = dynamic([
"/Library/LaunchDaemons/",
"/System/Library/LaunchDaemons/",
"/Library/LaunchAgents/",
"/System/Library/LaunchAgents/"
]);
let UserLaunchAgentPattern = "/Library/LaunchAgents/";
let SuspiciousParents = dynamic([
"bash", "sh", "zsh", "python", "python3", "ruby", "perl",
"curl", "wget", "osascript", "node"
]);
// Detect plist file creation in LaunchDaemon/LaunchAgent directories
let PlistFileCreation = DeviceFileEvents
| where Timestamp > ago(24h)
| where OSPlatform =~ "macOS" or DeviceType =~ "Mac"
| where FolderPath has_any (LaunchDaemonPaths)
| where FileName endswith ".plist"
| where ActionType in ("FileCreated", "FileModified", "FileRenamed")
| extend AlertType = "PlistCreatedInLaunchDirectory"
| extend IsDaemon = FolderPath has "/Library/LaunchDaemons/"
| extend IsSystemPath = FolderPath has "/System/Library/"
| project Timestamp, DeviceName, AccountName, FileName, FolderPath,
InitiatingProcessFileName, InitiatingProcessCommandLine,
InitiatingProcessAccountName, ActionType, AlertType, IsDaemon, IsSystemPath;
// Detect suspicious launchctl load/bootstrap commands
let LaunchctlSuspicious = DeviceProcessEvents
| where Timestamp > ago(24h)
| where OSPlatform =~ "macOS" or DeviceType =~ "Mac"
| where FileName =~ "launchctl"
| where ProcessCommandLine has_any ("load", "bootstrap", "submit", "start")
| where InitiatingProcessFileName has_any (SuspiciousParents)
or ProcessCommandLine has_any ("/tmp/", "/var/tmp/", "/dev/shm", ".hidden",
"curl", "wget", "base64", "/Users/Shared/")
| extend AlertType = "SuspiciousLaunchctlExecution"
| extend IsDaemon = ProcessCommandLine has "/Library/LaunchDaemons/"
| extend IsSystemPath = ProcessCommandLine has "/System/Library/"
| project Timestamp, DeviceName, AccountName, FileName, ProcessCommandLine,
InitiatingProcessFileName, InitiatingProcessCommandLine,
InitiatingProcessAccountName, AlertType, IsDaemon, IsSystemPath;
// Union both detections
PlistFileCreation
| extend ProcessCommandLine = InitiatingProcessCommandLine
| union (LaunchctlSuspicious
| extend FileName = FileName, FolderPath = "", ActionType = "ProcessCreated")
| sort by Timestamp descDetects launchd abuse on macOS by monitoring for plist file creation or modification in LaunchDaemon and LaunchAgent directories, as well as suspicious launchctl commands used to load or bootstrap services. Identifies files created by unexpected parent processes (shells, scripting interpreters, download utilities) and launchctl invocations with suspicious paths or initiated from known-risky parent processes. Requires Microsoft Defender for Endpoint with macOS device coverage.
Data Sources
Required Tables
False Positives & Tuning
- Legitimate software installation (Homebrew, macOS app installers, enterprise MDM) creating plist files in LaunchDaemons or LaunchAgents directories
- IT management tools (Jamf Pro, Puppet, Chef, Ansible) deploying configuration via launchctl load as part of policy enforcement
- Developer tools and package managers (e.g., Homebrew services) that register background services using plist files
- macOS system updates modifying plist files in /System/Library paths
- Monitoring agents (CrowdStrike, Carbon Black, SentinelOne endpoint sensors) installing their own LaunchDaemon plist files
Other platforms for T1053.004
Testing Methodology
Validate this detection against 4 adversary techniques from Atomic Red Team. Each test below lists the behaviour to exercise and the telemetry you should expect to see. Executable commands and cleanup steps are available with Pro.
- Test 1Create Malicious LaunchAgent Plist for User Persistence
Expected signal: File creation event for ~/Library/LaunchAgents/com.argus.test.persistence.plist and /tmp/argus_test_payload.sh. Process creation event for launchctl with arguments 'load ~/Library/LaunchAgents/com.argus.test.persistence.plist'. macOS Unified Log entry for launchd registering the new service with label 'com.argus.test.persistence'. Subsequent execution of /bin/bash with /tmp/argus_test_payload.sh as argument, initiated by launchd.
- Test 2Create Root LaunchDaemon Plist for System-Level Persistence
Expected signal: File creation event for /Library/LaunchDaemons/com.argus.test.daemon.plist with initiating process sudo/bash running as root. Process creation events for sudo and launchctl with 'load /Library/LaunchDaemons/com.argus.test.daemon.plist'. macOS Unified Log entry from launchd registering system daemon. The IsDaemon flag in the KQL query should be set to true.
- Test 3Launchctl Load from Suspicious Temp Directory Path
Expected signal: File creation event for /tmp/com.argus.tmppersist.plist. Process creation event for launchctl with command line containing 'load /tmp/com.argus.tmppersist.plist' — the /tmp path is a key indicator. macOS Unified Log entries for launchd service registration from a temp path.
- Test 4Simulate Adversary Plist Drop via curl and Shell
Expected signal: Process creation for bash with the dropper script as command. File creation event for ~/Library/LaunchAgents/com.argus.dropper.test.plist with InitiatingProcessFileName=bash — the suspicious parent detection fires. Process creation for launchctl initiated by bash. macOS Unified Log shows the full execution chain: bash → file write → launchctl → launchd registration.
References (10)
- https://attack.mitre.org/techniques/T1053/004/
- https://developer.apple.com/library/content/documentation/MacOSX/Conceptual/BPSystemStartup/Chapters/CreatingLaunchdJobs.html
- https://www.virusbulletin.com/uploads/pdf/conference/vb2014/VB2014-Wardle.pdf
- https://objective-see.org/blog.html
- https://github.com/redcanaryco/atomic-red-team/blob/master/atomics/T1053.004/T1053.004.md
- https://www.sentinelone.com/blog/how-malware-persists-on-macos/
- https://www.crowdstrike.com/blog/how-to-detect-and-prevent-mac-malware/
- https://managingosx.wordpress.com/2015/10/15/launchd-is-not-a-valid-way-to-run-a-job-at-a-scheduled-time/
- https://support.apple.com/guide/terminal/apdc6c1077b-5d5d-4d35-9c19-60f2397b2369/mac
- https://github.com/SigmaHQ/sigma/tree/master/rules/macos
Unlock Pro Content
Get the full detection package for T1053.004 including response playbook, investigation guide, and atomic red team tests.