> 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/uncommon-msiexec-execution-of-an-arbitrary-file-from-a-remote-location.md).

# Uncommon msiexec execution of an arbitrary file from a remote location

### 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        | LOLBIN Execution Analytics                         |
| ATT\&CK Tactic       | Stealth (TA0005)                                   |
| ATT\&CK Technique    | System Binary Proxy Execution: Msiexec (T1218.007) |
| Severity             | Low                                                |

### Description

Msiexec is the command-line utility for the Windows Installer. Adversaries may abuse msiexec.exe to proxy execution of malicious payloads from remote locations.

### Attacker's Goals

Evading security controls and executing arbitrary files from the web.

### Investigative actions

Monitor the command-line arguments of msiexec.exe, For example, the command line msiexec /i <http://some\\_domain.com/www/executable.msi> can be legitimate or malicious.

* Check if the the URL that is encoded in the command line is trusted.
* Determine if the executed DLL or MSI file is known as legitimate.
* Confirm whether the initiating process is legitimate and if the user running it knows of its use. Note - the MSI executable can run from other LAN locations, the alert will raise on the WAN connection.

### Variations

<details>

<summary>Suspicious msiexec execution on an internet-facing endpoint</summary>

**Synopsis**

| Field             | Value                                              |
| ----------------- | -------------------------------------------------- |
| ATT\&CK Tactic    | Stealth (TA0005)                                   |
| ATT\&CK Technique | System Binary Proxy Execution: Msiexec (T1218.007) |
| Severity          | Low                                                |

**Description**

Suspicious msiexec execution of an arbitrary file from the web on an internet-facing server.

**Attacker's Goals**

Evading security controls and executing arbitrary files from the web.

**Investigative actions**

Monitor the command-line arguments of msiexec.exe, For example, the command line msiexec /i <http://some\\_domain.com/www/executable.msi> can be legitimate or malicious.

* Check if the the URL that is encoded in the command line is trusted.
* Determine if the executed DLL or MSI file is known as legitimate.
* Confirm whether the initiating process is legitimate and if the user running it knows of its use. Note - the MSI executable can run from other LAN locations, the alert will raise on the WAN connection.

</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/uncommon-msiexec-execution-of-an-arbitrary-file-from-a-remote-location.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.