> 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/suspicious-process-loads-a-known-powershell-module.md).

# Suspicious process loads a known PowerShell module

### Synopsis

| Field                | Value                                                     |
| -------------------- | --------------------------------------------------------- |
| Activation Period    | 14 Days                                                   |
| Training Period      | 30 Days                                                   |
| Test Period          | N/A (single event)                                        |
| Deduplication Period | 8 Hours                                                   |
| Required Data        | XDR Agent                                                 |
| ATT\&CK Tactic       | Execution (TA0002)                                        |
| ATT\&CK Technique    | Command and Scripting Interpreter: PowerShell (T1059.001) |
| Severity             | Informational                                             |

### Description

A non-PowerShell process loaded a known PowerShell module. This image load may be an indication of PowerShell execution without directly invoking the PowerShell.exe binary.

### Attacker's Goals

An attacker is attempting to run PowerShell without PowerShell.exe to evade detection.

### Investigative actions

Investigate the process and command line executed and whether it's benign or normal for this host.

### Variations

<details>

<summary>Suspicious unsigned process loads a known PowerShell module</summary>

**Synopsis**

| Field             | Value                                                     |
| ----------------- | --------------------------------------------------------- |
| ATT\&CK Tactic    | Execution (TA0002)                                        |
| ATT\&CK Technique | Command and Scripting Interpreter: PowerShell (T1059.001) |
| Severity          | Low                                                       |

**Description**

A non-PowerShell process loaded a known PowerShell module. This image load may be an indication of PowerShell execution without directly invoking the PowerShell.exe binary.

**Attacker's Goals**

An attacker is attempting to run PowerShell without PowerShell.exe to evade detection.

**Investigative actions**

Investigate the process and command line executed and whether it's benign or normal for this host.

</details>

<details>

<summary>Office process loads a known PowerShell DLL</summary>

**Synopsis**

| Field             | Value                                                     |
| ----------------- | --------------------------------------------------------- |
| ATT\&CK Tactic    | Execution (TA0002)                                        |
| ATT\&CK Technique | Command and Scripting Interpreter: PowerShell (T1059.001) |
| Severity          | High                                                      |

**Description**

A Microsoft Office process loaded a known PowerShell module. This image load may be a sign of PowerShell execution without directly invoking the PowerShell.exe binary.

**Attacker's Goals**

An attacker is attempting to run PowerShell without PowerShell.exe to evade detection.

**Investigative actions**

Investigate the process and command line executed and whether it's benign or normal for this host.

</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/suspicious-process-loads-a-known-powershell-module.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.