> 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-search-order-hijacking.md).
# Possible DLL Search Order Hijacking
### 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 | Stealth (TA0005) |
| ATT\&CK Technique | Hijack Execution Flow: DLL (T1574.001), Hijack Execution Flow: Path Interception by PATH Environment Variable (T1574.007), Hijack Execution Flow: Path Interception by Unquoted Path (T1574.009), Hijack Execution Flow: Path Interception by Search Order Hijacking (T1574.008) |
| Severity | Low |
### Description
An attacker might abuse the Windows DLL search order to trigger known, signed processes to load the attacker's malicious module.
### 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
Possible DLL Search Order Hijacking by DLL Substitution
**Synopsis**
| Field | Value |
| ----------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| ATT\&CK Tactic | Stealth (TA0005) |
| ATT\&CK Technique | Hijack Execution Flow: DLL (T1574.001), Hijack Execution Flow: Path Interception by PATH Environment Variable (T1574.007), Hijack Execution Flow: Path Interception by Unquoted Path (T1574.009), Hijack Execution Flow: Path Interception by Search Order Hijacking (T1574.008), Masquerading (T1036), Masquerading: Match Legitimate Resource Name or Location (T1036.005) |
| Severity | Low |
**Description**
An attacker might abuse the Windows DLL search order to trigger known, signed processes to load the attacker's malicious module.
**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.
Possible DLL Search Order Hijacking - DLL extracted from an internet-downloaded archive
**Synopsis**
| Field | Value |
| ----------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| ATT\&CK Tactic | Stealth (TA0005) |
| ATT\&CK Technique | Hijack Execution Flow: DLL (T1574.001), Hijack Execution Flow: Path Interception by PATH Environment Variable (T1574.007), Hijack Execution Flow: Path Interception by Unquoted Path (T1574.009), Hijack Execution Flow: Path Interception by Search Order Hijacking (T1574.008) |
| Severity | Low |
**Description**
An attacker might abuse the Windows DLL search order to trigger known, signed processes to load the attacker's malicious module.
**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.
Possible DLL Search Order Hijacking - DLL downloaded from an uncommon source
**Synopsis**
| Field | Value |
| ----------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| ATT\&CK Tactic | Stealth (TA0005) |
| ATT\&CK Technique | Hijack Execution Flow: DLL (T1574.001), Hijack Execution Flow: Path Interception by PATH Environment Variable (T1574.007), Hijack Execution Flow: Path Interception by Unquoted Path (T1574.009), Hijack Execution Flow: Path Interception by Search Order Hijacking (T1574.008) |
| Severity | Low |
**Description**
An attacker might abuse the Windows DLL search order to trigger known, signed processes to load the attacker's malicious module.
**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.
---
# 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/possible-dll-search-order-hijacking.md?ask=&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.