> 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/execution-of-dllhost-exe-with-an-empty-command-line.md).

# Execution of dllhost.exe with an empty 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        | LOLBIN Execution Analytics            |
| ATT\&CK Tactic       | Stealth (TA0005)                      |
| ATT\&CK Technique    | System Binary Proxy Execution (T1218) |
| Severity             | Low                                   |

### Description

The process dllhost.exe was executed with an empty command line. This behavior is suspicious, and may be caused by a malicious actor using 'Image File Execution Options' in the registry to evade detection.

### Attacker's Goals

Evade detection when running suspicious commands.

### Investigative actions

* Check if an entry for dllhost.exe was added in the registry, under HKEY\_LOCAL\_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Image File Execution Options.

### Variations

<details>

<summary>Execution of unsigned dllhost from a non-typical path with empty command line</summary>

**Synopsis**

| Field             | Value                                                |
| ----------------- | ---------------------------------------------------- |
| ATT\&CK Tactic    | Stealth (TA0005)                                     |
| ATT\&CK Technique | Masquerading: Masquerade Task or Service (T1036.004) |
| Severity          | High                                                 |

**Description**

An unsigned process was executed with the name dllhost.exe from a non-typical path, this behavior is suspicious and maybe performed by a malicious actor in an attempt to hide their actions.

**Attacker's Goals**

Evade detection when performing suspicious actions.

**Investigative actions**

* Review actions performed by the executed process and the causality owner, and check if they are suspicious.

</details>

<details>

<summary>Globally uncommon execution of dllhost.exe with an empty command line</summary>

**Synopsis**

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

**Description**

The process dllhost.exe was executed with an empty command line. This behavior is suspicious, and may be caused by a malicious actor using 'Image File Execution Options' in the registry to evade detection.

**Attacker's Goals**

Evade detection when running suspicious commands.

**Investigative actions**

* Check if an entry for dllhost.exe was added in the registry, under HKEY\_LOCAL\_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Image File Execution Options.

</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/execution-of-dllhost-exe-with-an-empty-command-line.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.