> 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/phantom-dll-loading.md).

# Phantom DLL Loading

### 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        | DLL Hijacking Analytics                |
| ATT\&CK Tactic       | Persistence (TA0003)                   |
| ATT\&CK Technique    | Hijack Execution Flow: DLL (T1574.001) |
| Severity             | Medium                                 |

### Description

An attacker might leverage existing processes missing module loads to load malicious code into trusted processes.

### Attacker's Goals

An attacker is attempting to load untrusted code into trusted contexts to avoid detection, persist or escalate privileges.

### Investigative actions

Investigate the loaded module and verify if it is malicious.

### Variations

<details>

<summary>Phantom DLL Loading was used to load a DLL into a process after it was extracted from an internet-downloaded archive</summary>

**Synopsis**

| Field             | Value                                  |
| ----------------- | -------------------------------------- |
| ATT\&CK Tactic    | Persistence (TA0003)                   |
| ATT\&CK Technique | Hijack Execution Flow: DLL (T1574.001) |
| Severity          | High                                   |

**Description**

An attacker might leverage existing processes missing module loads to load malicious code into trusted processes.

**Attacker's Goals**

An attacker is attempting to load untrusted code into trusted contexts to avoid detection, persist or escalate privileges.

**Investigative actions**

Investigate the loaded module and verify if it is malicious.

</details>

<details>

<summary>Phantom DLL Loading was used to load a DLL into a process after it was downloaded from an uncommon source</summary>

**Synopsis**

| Field             | Value                                  |
| ----------------- | -------------------------------------- |
| ATT\&CK Tactic    | Persistence (TA0003)                   |
| ATT\&CK Technique | Hijack Execution Flow: DLL (T1574.001) |
| Severity          | High                                   |

**Description**

An attacker might leverage existing processes missing module loads to load malicious code into trusted processes.

**Attacker's Goals**

An attacker is attempting to load untrusted code into trusted contexts to avoid detection, persist or escalate privileges.

**Investigative actions**

Investigate the loaded module and verify if it is malicious.

</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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://cortex-docs.paloaltonetworks.com/analytics-alerts/alerts-by-name/phantom-dll-loading.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
