Try it using Invoke-Atomic

Create or Modify System Process: Launch Daemon

Description from ATT&CK

Adversaries may create or modify Launch Daemons to execute malicious payloads as part of persistence. Launch Daemons are plist files used to interact with Launchd, the service management framework used by macOS. Launch Daemons require elevated privileges to install, are executed for every user on a system prior to login, and run in the background without the need for user interaction. During the macOS initialization startup, the launchd process loads the parameters for launch-on-demand system-level daemons from plist files found in /System/Library/LaunchDaemons/ and /Library/LaunchDaemons/. Required Launch Daemons parameters include a Label to identify the task, Program to provide a path to the executable, and RunAtLoad to specify when the task is run. Launch Daemons are often used to provide access to shared resources, updates to software, or conduct automation tasks.(Citation: AppleDocs Launch Agent Daemons)(Citation: Methods of Mac Malware Persistence)(Citation: launchd Keywords for plists)

Adversaries may install a Launch Daemon configured to execute at startup by using the RunAtLoad parameter set to true and the Program parameter set to the malicious executable path. The daemon name may be disguised by using a name from a related operating system or benign software (i.e. Masquerading). When the Launch Daemon is executed, the program inherits administrative permissions.(Citation: WireLurker)(Citation: OSX Malware Detection)

Additionally, system configuration changes (such as the installation of third party package managing software) may cause folders such as usr/local/bin to become globally writeable. So, it is possible for poor configurations to allow an adversary to modify executables referenced by current Launch Daemon's plist files.(Citation: LaunchDaemon Hijacking)(Citation: sentinelone macos persist Jun 2019)

Atomic Tests

Atomic Test #1 - Launch Daemon

Utilize LaunchDaemon to launch

1
Hello World

Supported Platforms: macos

auto_generated_guid: 03ab8df5-3a6b-4417-b6bd-bb7a5cfd74cf

Inputs:

Name Description Type Default Value
plist_filename filename String com.atomicredteam.plist
path_malicious_plist Name of file to store in cron folder String $PathToAtomicsFolder/T1543.004/src/atomicredteam_T1543_004.plist

Attack Commands: Run with bash! Elevation Required (e.g. root or admin)

1
2
3
sudo cp #{path_malicious_plist} /Library/LaunchDaemons/#{plist_filename}
sudo launchctl load -w /Library/LaunchDaemons/#{plist_filename}

Cleanup Commands:

1
2
3
4
sudo launchctl unload /Library/LaunchDaemons/#{plist_filename}
sudo rm /Library/LaunchDaemons/#{plist_filename}
sudo rm /tmp/T1543_004_atomicredteam.txt

Dependencies: Run with bash!

Description: The shared library must exist on disk at specified location (#{path_malicious_plist})

Check Prereq Commands:

1
2
if [ -f #{path_malicious_plist} ]; then exit 0; else exit 1; fi;

Get Prereq Commands:

1
2
echo "The plist file doesn't exist. Check the path and try again."; exit 1;

source