T1569.001 Google Chronicle · YARA-L

Detect Launchctl in Google Chronicle

Adversaries may abuse launchctl to execute commands or programs on macOS. Launchctl interfaces with launchd, the macOS service management framework, and supports subcommands including load, unload, start, stop, and kickstart. Adversaries use launchctl to execute payloads as Launch Agents (per-user persistence in ~/Library/LaunchAgents/ or /Library/LaunchAgents/) or Launch Daemons (system-level persistence in /Library/LaunchDaemons/). Common attack patterns include loading malicious plist files from world-writable directories such as /tmp, using the -w flag to force-enable disabled services, and invoking launchctl from scripting engines after initial access. Real-world threat actors using this technique include LoudMiner (QEMU-based cryptominer), Cuckoo Stealer, AppleJeus (North Korean cryptocurrency theft), macOS.OSAMiner, XCSSET (Xcode project infection), and Calisto spyware.

MITRE ATT&CK

Tactic
Execution
Technique
T1569 System Services
Sub-technique
T1569.001 Launchctl
Canonical reference
https://attack.mitre.org/techniques/T1569/001/

YARA-L Detection Query

Google Chronicle (YARA-L)
yaral
rule t1569_001_launchctl_abuse {
  meta:
    author = "Argus Detection Engineering"
    description = "Detects T1569.001 launchctl abuse on macOS — suspicious launchctl invocations loading from temp paths, invoked by scripting engines, or using force-load flags with user LaunchAgent directories"
    mitre_attack_technique = "T1569.001"
    mitre_attack_tactic = "Execution"
    severity = "HIGH"
    confidence = "HIGH"
    version = "1.0"
    created = "2026-04-21"

  events:
    $e.metadata.event_type = "PROCESS_LAUNCH"
    $e.target.process.file.full_path = /\/usr\/bin\/launchctl|\/bin\/launchctl/
    (
      $e.target.process.command_line = /launchctl\s+(load|start|kickstart|bootstrap)/
      or $e.target.process.file.full_path = /launchctl/
    )
    (
      $e.target.process.command_line = /\/tmp\/|\/private\/tmp\/|\/var\/tmp\/|\/var\/folders\/|\/Users\/Shared\//
      or $e.principal.process.file.full_path = /(bash|sh|zsh|ksh|fish|python[0-9.]*|ruby|perl|osascript|curl|wget|node|npm)$/
      or (
        $e.target.process.command_line = /\-w/
        and $e.target.process.command_line = /\/Users\/[^\/]+\/Library\/LaunchAgents\//
      )
    )

  condition:
    $e
}
high severity high confidence

Chronicle YARA-L 2.0 rule detecting T1569.001 launchctl abuse on macOS. Monitors PROCESS_LAUNCH UDM events for launchctl executions that load from world-writable temporary directories, are spawned by scripting engines or network utilities, or use force-load (-w) with user-scoped LaunchAgent paths. Covers known threat actor TTPs from LoudMiner, Cuckoo Stealer, AppleJeus, XCSSET, and Calisto.

Data Sources

Google Chronicle SIEMChronicle Unified Data Model (UDM)macOS endpoint telemetry via Chronicle forwarder

Required Tables

PROCESS_LAUNCH UDM events

False Positives & Tuning

  • Enterprise MDM solutions (Jamf, Mosyle, Kandji) that deploy configuration profiles and service registrations using launchctl via managed shell scripts on enrolled macOS endpoints
  • Software development environments where build scripts or test runners launch background services using launchctl, particularly in organizations with active macOS development teams
  • IT automation tools (Ansible, Terraform) managing macOS fleet configuration that run launchctl commands through scripted playbooks during maintenance windows
Download portable Sigma rule (.yml)

Other platforms for T1569.001


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.

  1. Test 1Load LaunchAgent from /tmp (Malware Staging Pattern)

    Expected signal: Process creation: launchctl with ProcessCommandLine containing 'load /tmp/com.df00tech.atomictest.plist'; parent process is the executing shell. Secondary process creation: /bin/sh spawned by launchd executing the RunAtLoad ProgramArguments. File creation: /tmp/launchctl_test_output.txt written by the loaded agent. macOS Unified Log entry for com.df00tech.atomictest service start under the current user's launchd domain.

  2. Test 2Load LaunchDaemon with Force-Enable Flag (-w) — XCSSET and LoudMiner Technique

    Expected signal: Process creation: sudo followed by launchctl with ProcessCommandLine containing 'load -w /Library/LaunchDaemons/com.df00tech.daemontest.plist'. File creation event in /Library/LaunchDaemons/ directory (anomalous outside MDM-managed deployments). launchd override database updated at /var/db/launchd.db/. macOS Unified Log records bootstrap of com.df00tech.daemontest in the system launchd domain.

  3. Test 3Enable Screen Sharing via Launchctl — Calisto Spyware Technique

    Expected signal: Process creation: launchctl with ProcessCommandLine 'load -w /System/Library/LaunchDaemons/com.apple.screensharing.plist'. Parent process is sudo/shell. macOS Unified Log records screensharing daemon activation. System Preferences -> Sharing would show Screen Sharing enabled. VNC listener appears on TCP port 5900 (detectable via network telemetry). launchd override database records screensharing as enabled.

  4. Test 4Launchctl Invoked from Python Dropper (Staged Execution Chain)

    Expected signal: Process creation chain: python3 spawning /bin/launchctl as a child process. ProcessCommandLine for launchctl: 'load /tmp/com.df00tech.pytest.plist'. InitiatingProcessFileName: python3. This specific parent-child relationship (python3 → launchctl) is the key detection signal. Secondary process creation: /bin/sh running the ProgramArguments payload, spawned by launchd.

Unlock Pro Content

Get the full detection package for T1569.001 including response playbook, investigation guide, and atomic red team tests.

Response PlaybookInvestigation GuideHunting QueriesAtomic Red Team TestsTuning Guidance

Related Detections