> 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/a-contained-executable-was-executed-by-an-unusual-process.md).

# A contained executable was executed by an unusual process

### 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                                                                                            |
| ATT\&CK Tactic       | Privilege Escalation (TA0004), Persistence (TA0003)                                                  |
| ATT\&CK Technique    | Escape to Host (T1611), Boot or Logon Autostart Execution: Kernel Modules and Extensions (T1547.006) |
| Severity             | Medium                                                                                               |

### Description

A Docker-contained executable from a mounted share was executed on a host. Running a contained executable is highly dangerous and atypical.

### Attacker's Goals

Gain high privileged command execution on the host machine via one of its running containers.

### Investigative actions

* Check what actions were made after the suspicious file execution.
* Investigate the contained process and its process tree.

### Variations

<details>

<summary>A contained executable was executed by the Linux kernel thread daemon</summary>

**Synopsis**

| Field             | Value                                                                                                |
| ----------------- | ---------------------------------------------------------------------------------------------------- |
| ATT\&CK Tactic    | Privilege Escalation (TA0004), Persistence (TA0003)                                                  |
| ATT\&CK Technique | Escape to Host (T1611), Boot or Logon Autostart Execution: Kernel Modules and Extensions (T1547.006) |
| Severity          | High                                                                                                 |

**Description**

A contained executable in a cloud machine was executed by the Linux kernel thread daemon. This behavior is suspicious as it may be a result of an attacker attempting to escape from a container, as the kernel thread daemon is usually used to spawn kernel processes only.

**Attacker's Goals**

Gain high privileged command execution on the host machine via one of its running containers.

**Investigative actions**

* Check what actions were made after the suspicious file execution.
* Investigate the contained process and its process tree.

</details>

<details>

<summary>A contained executable was executed by the Linux kernel thread daemon</summary>

**Synopsis**

| Field             | Value                                                                                                |
| ----------------- | ---------------------------------------------------------------------------------------------------- |
| ATT\&CK Tactic    | Privilege Escalation (TA0004), Persistence (TA0003)                                                  |
| ATT\&CK Technique | Escape to Host (T1611), Boot or Logon Autostart Execution: Kernel Modules and Extensions (T1547.006) |
| Severity          | High                                                                                                 |

**Description**

A contained executable was executed by the Linux kernel thread daemon. This behavior is suspicious as it may be a result of an attacker attempting to escape from a container, as the kernel thread daemon is usually used to spawn kernel processes only.

**Attacker's Goals**

Gain high privileged command execution on the host machine via one of its running containers.

**Investigative actions**

* Check what actions were made after the suspicious file execution.
* Investigate the contained process and its process tree.

</details>

<details>

<summary>A contained executable was executed by an unusual process</summary>

**Synopsis**

| Field             | Value                                                                                                |
| ----------------- | ---------------------------------------------------------------------------------------------------- |
| ATT\&CK Tactic    | Privilege Escalation (TA0004), Persistence (TA0003)                                                  |
| ATT\&CK Technique | Escape to Host (T1611), Boot or Logon Autostart Execution: Kernel Modules and Extensions (T1547.006) |
| Severity          | Medium                                                                                               |

**Description**

A Docker-contained executable from a mounted share on a cloud machine was executed on a host. Running a contained executable is highly dangerous and atypical.

**Attacker's Goals**

Gain high privileged command execution on the host machine via one of its running containers.

**Investigative actions**

* Check what actions were made after the suspicious file execution.
* Investigate the contained process and its process tree.

</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/a-contained-executable-was-executed-by-an-unusual-process.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.
