> 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/clickfix-powershell-executed-through-the-run-application.md).

# ClickFix - PowerShell executed through the run application

### 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 with eXtended Threat Hunting (XTH) |
| ATT\&CK Tactic       | Execution (TA0002), Initial Access (TA0001)  |
| ATT\&CK Technique    | User Execution (T1204), Phishing (T1566)     |
| Severity             | Low                                          |

### Description

An attacker may be trying to trick a user to execute PowerShell through the run application.

### Attacker's Goals

* An attacker may be trying to trick a user to execute PowerShell through the run application.

### Investigative actions

* Check if the command line is known in the organization or malicious.
* And ask the user what is the source of it.

### Variations

<details>

<summary>ClickFix - PowerShell command executed through the run application and using Invoke-Expression cmdlet</summary>

**Synopsis**

| Field             | Value                                       |
| ----------------- | ------------------------------------------- |
| ATT\&CK Tactic    | Execution (TA0002), Initial Access (TA0001) |
| ATT\&CK Technique | User Execution (T1204), Phishing (T1566)    |
| Severity          | High                                        |

**Description**

An attacker may be trying to trick a user to execute PowerShell through the run application.

**Attacker's Goals**

* An attacker may be trying to trick a user to execute PowerShell through the run application.

**Investigative actions**

* Check if the command line is known in the organization or malicious.
* And ask the user what is the source of it.

</details>

<details>

<summary>ClickFix - Long PowerShell command executed through the run application with URL in the command</summary>

**Synopsis**

| Field             | Value                                       |
| ----------------- | ------------------------------------------- |
| ATT\&CK Tactic    | Execution (TA0002), Initial Access (TA0001) |
| ATT\&CK Technique | User Execution (T1204), Phishing (T1566)    |
| Severity          | High                                        |

**Description**

An attacker may be trying to trick a user to execute PowerShell through the run application.

**Attacker's Goals**

* An attacker may be trying to trick a user to execute PowerShell through the run application.

**Investigative actions**

* Check if the command line is known in the organization or malicious.
* And ask the user what is the source of it.

</details>

<details>

<summary>ClickFix - Long encoded PowerShell command executed through the run application</summary>

**Synopsis**

| Field             | Value                                       |
| ----------------- | ------------------------------------------- |
| ATT\&CK Tactic    | Execution (TA0002), Initial Access (TA0001) |
| ATT\&CK Technique | User Execution (T1204), Phishing (T1566)    |
| Severity          | High                                        |

**Description**

An attacker may be trying to trick a user to execute PowerShell through the run application.

**Attacker's Goals**

* An attacker may be trying to trick a user to execute PowerShell through the run application.

**Investigative actions**

* Check if the command line is known in the organization or malicious.
* And ask the user what is the source of it.

</details>

<details>

<summary>ClickFix - Schedule task PowerShell command executed through the run application</summary>

**Synopsis**

| Field             | Value                                       |
| ----------------- | ------------------------------------------- |
| ATT\&CK Tactic    | Execution (TA0002), Initial Access (TA0001) |
| ATT\&CK Technique | User Execution (T1204), Phishing (T1566)    |
| Severity          | High                                        |

**Description**

An attacker may be trying to trick a user to execute PowerShell through the run application.

**Attacker's Goals**

* An attacker may be trying to trick a user to execute PowerShell through the run application.

**Investigative actions**

* Check if the command line is known in the organization or malicious.
* And ask the user what is the source of it.

</details>


---

# 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/clickfix-powershell-executed-through-the-run-application.md?ask=<question>&goal=<user_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.
