> 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/possible-dll-hijack-into-a-microsoft-process.md).

# Possible DLL Hijack into a Microsoft 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                                                                     |
| Detector Tags        | DLL Hijacking Analytics                                                       |
| ATT\&CK Tactic       | Persistence (TA0003), Privilege Escalation (TA0004), Defense Evasion (TA0005) |
| ATT\&CK Technique    | Hijack Execution Flow: DLL (T1574.001)                                        |
| Severity             | Informational                                                                 |

### Description

An unsigned DLL was loaded into a Microsoft signed process. This DLL name is usually signed by Microsoft, which might indicate an attacker performing DLL Hijacking.

### Attacker's Goals

An attacker is attempting to load an untrusted module into a trusted context to avoid detection, gain persistence or to perform privilege escalation.

### Investigative actions

* Investigate the loaded module to verify if it is malicious.
* Investigate if the loading process and the loaded module reside in legitimate locations.

### Variations

<details>

<summary>Possible DLL Hijack of a low entropy DLL into a Microsoft process</summary>

**Synopsis**

| Field             | Value                                                                                               |
| ----------------- | --------------------------------------------------------------------------------------------------- |
| ATT\&CK Tactic    | Persistence (TA0003), Privilege Escalation (TA0004), Defense Evasion (TA0005)                       |
| ATT\&CK Technique | Hijack Execution Flow: DLL (T1574.001), Obfuscated Files or Information: Binary Padding (T1027.001) |
| Severity          | Informational                                                                                       |

**Description**

An unsigned DLL was loaded into a Microsoft signed process. This DLL name is usually signed by Microsoft, which might indicate an attacker performing DLL Hijacking.

**Attacker's Goals**

An attacker is attempting to load an untrusted module into a trusted context to avoid detection, gain persistence or to perform privilege escalation.

**Investigative actions**

* Investigate the loaded module to verify if it is malicious.
* Investigate if the loading process and the loaded module reside in legitimate locations.

</details>

<details>

<summary>Possible DLL Side-Loading into a Microsoft process from a suspicious folder</summary>

**Synopsis**

| Field             | Value                                                                          |
| ----------------- | ------------------------------------------------------------------------------ |
| ATT\&CK Tactic    | Persistence (TA0003), Privilege Escalation (TA0004), Defense Evasion (TA0005)  |
| ATT\&CK Technique | Hijack Execution Flow: DLL (T1574.001), Hijack Execution Flow: DLL (T1574.001) |
| Severity          | Informational                                                                  |

**Description**

An unsigned DLL was loaded into a Microsoft signed process. This DLL name is usually signed by Microsoft, which might indicate an attacker performing DLL Hijacking.

**Attacker's Goals**

An attacker is attempting to load an untrusted module into a trusted context to avoid detection, gain persistence or to perform privilege escalation.

**Investigative actions**

* Investigate the loaded module to verify if it is malicious.
* Investigate if the loading process and the loaded module reside in legitimate locations.

</details>

<details>

<summary>DLL Hijack into a Microsoft process</summary>

**Synopsis**

| Field             | Value                                                                         |
| ----------------- | ----------------------------------------------------------------------------- |
| ATT\&CK Tactic    | Persistence (TA0003), Privilege Escalation (TA0004), Defense Evasion (TA0005) |
| ATT\&CK Technique | Hijack Execution Flow: DLL (T1574.001)                                        |
| Severity          | Informational                                                                 |

**Description**

An unsigned DLL was loaded into a Microsoft signed process. This DLL name is usually signed by Microsoft, which might indicate an attacker performing DLL Hijacking.

**Attacker's Goals**

An attacker is attempting to load an untrusted module into a trusted context to avoid detection, gain persistence or to perform privilege escalation.

**Investigative actions**

* Investigate the loaded module to verify if it is malicious.
* Investigate if the loading process and the loaded module reside in legitimate locations.

</details>

<details>

<summary>Possible DLL Hijack into a Microsoft development or framework related process</summary>

**Synopsis**

| Field             | Value                                                                         |
| ----------------- | ----------------------------------------------------------------------------- |
| ATT\&CK Tactic    | Persistence (TA0003), Privilege Escalation (TA0004), Defense Evasion (TA0005) |
| ATT\&CK Technique | Hijack Execution Flow: DLL (T1574.001)                                        |
| Severity          | Informational                                                                 |

**Description**

An unsigned DLL was loaded into a Microsoft signed process. This DLL name is usually signed by Microsoft, which might indicate an attacker performing DLL Hijacking.

**Attacker's Goals**

An attacker is attempting to load an untrusted module into a trusted context to avoid detection, gain persistence or to perform privilege escalation.

**Investigative actions**

* Investigate the loaded module to verify if it is malicious.
* Investigate if the loading process and the loaded module reside in legitimate locations.

</details>

<details>

<summary>Possible DLL Hijack into a Microsoft process - the DLL was extracted from an internet-downloaded archive</summary>

**Synopsis**

| Field             | Value                                                                         |
| ----------------- | ----------------------------------------------------------------------------- |
| ATT\&CK Tactic    | Persistence (TA0003), Privilege Escalation (TA0004), Defense Evasion (TA0005) |
| ATT\&CK Technique | Hijack Execution Flow: DLL (T1574.001)                                        |
| Severity          | Informational                                                                 |

**Description**

An unsigned DLL was loaded into a Microsoft signed process. This DLL name is usually signed by Microsoft, which might indicate an attacker performing DLL Hijacking.

**Attacker's Goals**

An attacker is attempting to load an untrusted module into a trusted context to avoid detection, gain persistence or to perform privilege escalation.

**Investigative actions**

* Investigate the loaded module to verify if it is malicious.
* Investigate if the loading process and the loaded module reside in legitimate locations.

</details>

<details>

<summary>Possible DLL Hijack into a Microsoft process - the DLL downloaded from an uncommon source</summary>

**Synopsis**

| Field             | Value                                                                         |
| ----------------- | ----------------------------------------------------------------------------- |
| ATT\&CK Tactic    | Persistence (TA0003), Privilege Escalation (TA0004), Defense Evasion (TA0005) |
| ATT\&CK Technique | Hijack Execution Flow: DLL (T1574.001)                                        |
| Severity          | Informational                                                                 |

**Description**

An unsigned DLL was loaded into a Microsoft signed process. This DLL name is usually signed by Microsoft, which might indicate an attacker performing DLL Hijacking.

**Attacker's Goals**

An attacker is attempting to load an untrusted module into a trusted context to avoid detection, gain persistence or to perform privilege escalation.

**Investigative actions**

* Investigate the loaded module to verify if it is malicious.
* Investigate if the loading process and the loaded module reside in legitimate locations.

</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/possible-dll-hijack-into-a-microsoft-process.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.