> For the complete documentation index, see [llms.txt](https://cortex-docs.paloaltonetworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cortex-docs.paloaltonetworks.com/analytics-alerts/alerts-by-name/applescript-process-executed-with-a-rare-command-line.md).
# AppleScript process executed with a rare command line
### Synopsis
| Field | Value |
| -------------------- | ---------------------------------------------------------- |
| Activation Period | 14 Days |
| Training Period | 30 Days |
| Test Period | N/A (single event) |
| Deduplication Period | 1 Day |
| Required Data | XDR Agent |
| Detector Tags | AppleScript Analytics |
| ATT\&CK Tactic | Execution (TA0002) |
| ATT\&CK Technique | Command and Scripting Interpreter: AppleScript (T1059.002) |
| Severity | Informational |
### Description
The AppleScript interpreter process was executed with an uncommon command line.
### Attacker's Goals
Perform various actions via AppleScript code, such as establishing persistence, evading detection, executing secondary payloads or injecting remote processes.
### Investigative actions
* Analyze the command line and determine whether it performs any malicious or suspicious actions.
* Check the events generated by the process or its children for potential malicious behavior.
* Check whether the process was executed in an unusual way.
### Variations
AppleScript process executed with a rare command line containing uncommon arguments
**Synopsis**
| Field | Value |
| ----------------- | ---------------------------------------------------------- |
| ATT\&CK Tactic | Execution (TA0002) |
| ATT\&CK Technique | Command and Scripting Interpreter: AppleScript (T1059.002) |
| Severity | High |
**Description**
The AppleScript interpreter process was executed with an uncommon command line.
**Attacker's Goals**
Perform various actions via AppleScript code, such as establishing persistence, evading detection, executing secondary payloads or injecting remote processes.
**Investigative actions**
* Analyze the command line and determine whether it performs any malicious or suspicious actions.
* Check the events generated by the process or its children for potential malicious behavior.
* Check whether the process was executed in an unusual way.
AppleScript process executed with a rare command line possibly using Finder to perform operations
**Synopsis**
| Field | Value |
| ----------------- | ---------------------------------------------------------- |
| ATT\&CK Tactic | Execution (TA0002) |
| ATT\&CK Technique | Command and Scripting Interpreter: AppleScript (T1059.002) |
| Severity | High |
**Description**
The AppleScript interpreter process was executed with an uncommon command line.
**Attacker's Goals**
Perform various actions via AppleScript code, such as establishing persistence, evading detection, executing secondary payloads or injecting remote processes.
**Investigative actions**
* Analyze the command line and determine whether it performs any malicious or suspicious actions.
* Check the events generated by the process or its children for potential malicious behavior.
* Check whether the process was executed in an unusual way.
AppleScript process executed with a rare command line with an unusual password prompt
**Synopsis**
| Field | Value |
| ----------------- | ---------------------------------------------------------- |
| ATT\&CK Tactic | Execution (TA0002) |
| ATT\&CK Technique | Command and Scripting Interpreter: AppleScript (T1059.002) |
| Severity | Low |
**Description**
The AppleScript interpreter process was executed with an uncommon command line.
**Attacker's Goals**
Perform various actions via AppleScript code, such as establishing persistence, evading detection, executing secondary payloads or injecting remote processes.
**Investigative actions**
* Analyze the command line and determine whether it performs any malicious or suspicious actions.
* Check the events generated by the process or its children for potential malicious behavior.
* Check whether the process was executed in an unusual way.
AppleScript process executed with a rare command line that possibly injects JavaScript into a browser
**Synopsis**
| Field | Value |
| ----------------- | ---------------------------------------------------------- |
| ATT\&CK Tactic | Execution (TA0002) |
| ATT\&CK Technique | Command and Scripting Interpreter: AppleScript (T1059.002) |
| Severity | Low |
**Description**
The AppleScript interpreter process was executed with an uncommon command line.
**Attacker's Goals**
Perform various actions via AppleScript code, such as establishing persistence, evading detection, executing secondary payloads or injecting remote processes.
**Investigative actions**
* Analyze the command line and determine whether it performs any malicious or suspicious actions.
* Check the events generated by the process or its children for potential malicious behavior.
* Check whether the process was executed in an unusual way.
AppleScript process executed with a rare command line performing clipboard access
**Synopsis**
| Field | Value |
| ----------------- | ---------------------------------------------------------- |
| ATT\&CK Tactic | Execution (TA0002) |
| ATT\&CK Technique | Command and Scripting Interpreter: AppleScript (T1059.002) |
| Severity | Low |
**Description**
The AppleScript interpreter process was executed with an uncommon command line.
**Attacker's Goals**
Perform various actions via AppleScript code, such as establishing persistence, evading detection, executing secondary payloads or injecting remote processes.
**Investigative actions**
* Analyze the command line and determine whether it performs any malicious or suspicious actions.
* Check the events generated by the process or its children for potential malicious behavior.
* Check whether the process was executed in an unusual way.
AppleScript process executed with a rare command line that muted the audio output
**Synopsis**
| Field | Value |
| ----------------- | ---------------------------------------------------------- |
| ATT\&CK Tactic | Execution (TA0002) |
| ATT\&CK Technique | Command and Scripting Interpreter: AppleScript (T1059.002) |
| Severity | Low |
**Description**
The AppleScript interpreter process was executed with an uncommon command line.
**Attacker's Goals**
Perform various actions via AppleScript code, such as establishing persistence, evading detection, executing secondary payloads or injecting remote processes.
**Investigative actions**
* Analyze the command line and determine whether it performs any malicious or suspicious actions.
* Check the events generated by the process or its children for potential malicious behavior.
* Check whether the process was executed in an unusual way.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://cortex-docs.paloaltonetworks.com/analytics-alerts/alerts-by-name/applescript-process-executed-with-a-rare-command-line.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.