Suspicious LaunchAgent or LaunchDaemon Load via launchctl

PremiumReviewedSigma · Medium · v1
Product
macos
Category
process_creation
Author
HuntRule
Published
2026-07-21
Updated
2026-08-28

ATT&CK techniques

Persistence → Defense Evasion
  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Execution

  5. Cred Access

  6. Discovery

  7. Lateral Movement

  8. Collection

  9. C2

  10. Exfiltration

  11. Impact

What it detects

This rule detects launchctl loading a property list from a LaunchAgents or LaunchDaemons directory, the persistence mechanism most macOS malware uses to survive reboots. Registering a malicious plist ensures the payload is relaunched automatically by launchd under user or system context.

Related detections9 linkedT1543.001 — drag to rearrange
Suspicious Safari-Masquerading LaunchAgent Loaded via launchctl on macOS
Malicious XCSSET Payload Drop to Temp and Hidden Home Paths
Suspicious Zsh Persistence via zshrc_aliases Appended to Shell Startup (via process_creation)
Suspicious macOS Backdoor LaunchAgent launched Plist Persistence (via file_event)
Malicious macOS LaunchAgent Persistence via Masqueraded com.apple hcpi Property List
Malicious Telegram Update LaunchDaemon Persistence on macOS
Suspicious ClickLock LaunchAgent Persistence Plist Creation (via file_event)
Suspicious osascript LaunchAgent Plist Persistence for PhantomPulse on macOS
LaunchAgent or LaunchDaemon Persistence File Creation on macOS (via file_event)
Suspicious LaunchAgent or LaunchDaemon Load via launchctl
Pivot detection · T1543.001 · 9 related

Detection content is published as a reviewed draft. Tune thresholds and exclusions against your own telemetry before enabling this rule for alerting.