> 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/microsoft-office-injects-code-into-a-process.md).

# Microsoft Office injects code into a 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        | Injection Analytics                                                       |
| ATT\&CK Tactic       | Initial Access (TA0001), Defense Evasion (TA0005)                         |
| ATT\&CK Technique    | Phishing: Spearphishing Attachment (T1566.001), Process Injection (T1055) |
| Severity             | Low                                                                       |

### Description

An attacker may inject payloads into processes via Microsoft Office. While legitimate in certain cases, code injection can also be used in malicious ways.

### Attacker's Goals

* An attacker attempts to gain code execution via a phishing document.
* Attackers may inject code into processes to evade process-based defenses, as well as possibly elevate privileges.

### Investigative actions

* Check the source of the document (received by mail or loaded locally).
* Check whether the injecting process is benign and if this was a desired behavior as part of its normal execution flow.

### Variations

<details>

<summary>Unsigned Microsoft Office injects code into a process</summary>

**Synopsis**

| Field             | Value                                                                                                                                           |
| ----------------- | ----------------------------------------------------------------------------------------------------------------------------------------------- |
| ATT\&CK Tactic    | Initial Access (TA0001), Defense Evasion (TA0005)                                                                                               |
| ATT\&CK Technique | Phishing: Spearphishing Attachment (T1566.001), Process Injection (T1055), Masquerading: Match Legitimate Resource Name or Location (T1036.005) |
| Severity          | High                                                                                                                                            |

**Description**

An attacker may inject payloads into processes via Microsoft Office. While legitimate in certain cases, code injection can also be used in malicious ways.

**Attacker's Goals**

* An attacker attempts to gain code execution via a phishing document.
* Attackers may inject code into processes to evade process-based defenses, as well as possibly elevate privileges.

**Investigative actions**

* Check the source of the document (received by mail or loaded locally).
* Check whether the injecting process is benign and if this was a desired behavior as part of its normal execution flow.

</details>

<details>

<summary>Microsoft Office injects code into a process to a non-standard PE section</summary>

**Synopsis**

| Field             | Value                                                                     |
| ----------------- | ------------------------------------------------------------------------- |
| ATT\&CK Tactic    | Initial Access (TA0001), Defense Evasion (TA0005)                         |
| ATT\&CK Technique | Phishing: Spearphishing Attachment (T1566.001), Process Injection (T1055) |
| Severity          | High                                                                      |

**Description**

An attacker may inject payloads into processes via Microsoft Office. While legitimate in certain cases, code injection can also be used in malicious ways.

**Attacker's Goals**

* An attacker attempts to gain code execution via a phishing document.
* Attackers may inject code into processes to evade process-based defenses, as well as possibly elevate privileges.

**Investigative actions**

* Check the source of the document (received by mail or loaded locally).
* Check whether the injecting process is benign and if this was a desired behavior as part of its normal execution flow.

</details>

<details>

<summary>Microsoft Office injects code into a process to an undeclared memory page</summary>

**Synopsis**

| Field             | Value                                                                     |
| ----------------- | ------------------------------------------------------------------------- |
| ATT\&CK Tactic    | Initial Access (TA0001), Defense Evasion (TA0005)                         |
| ATT\&CK Technique | Phishing: Spearphishing Attachment (T1566.001), Process Injection (T1055) |
| Severity          | Medium                                                                    |

**Description**

An attacker may inject payloads into processes via Microsoft Office. While legitimate in certain cases, code injection can also be used in malicious ways.

**Attacker's Goals**

* An attacker attempts to gain code execution via a phishing document.
* Attackers may inject code into processes to evade process-based defenses, as well as possibly elevate privileges.

**Investigative actions**

* Check the source of the document (received by mail or loaded locally).
* Check whether the injecting process is benign and if this was a desired behavior as part of its normal execution flow.

</details>

<details>

<summary>Microsoft Office injects code into a process from an unsigned process</summary>

**Synopsis**

| Field             | Value                                                                     |
| ----------------- | ------------------------------------------------------------------------- |
| ATT\&CK Tactic    | Initial Access (TA0001), Defense Evasion (TA0005)                         |
| ATT\&CK Technique | Phishing: Spearphishing Attachment (T1566.001), Process Injection (T1055) |
| Severity          | Medium                                                                    |

**Description**

An attacker may inject payloads into processes via Microsoft Office. While legitimate in certain cases, code injection can also be used in malicious ways.

**Attacker's Goals**

* An attacker attempts to gain code execution via a phishing document.
* Attackers may inject code into processes to evade process-based defenses, as well as possibly elevate privileges.

**Investigative actions**

* Check the source of the document (received by mail or loaded locally).
* Check whether the injecting process is benign and if this was a desired behavior as part of its normal execution flow.

</details>

<details>

<summary>Microsoft Office macro-enabled spreadsheet (XLSM) injects code into a process</summary>

**Synopsis**

| Field             | Value                                                                     |
| ----------------- | ------------------------------------------------------------------------- |
| ATT\&CK Tactic    | Initial Access (TA0001), Defense Evasion (TA0005)                         |
| ATT\&CK Technique | Phishing: Spearphishing Attachment (T1566.001), Process Injection (T1055) |
| Severity          | Medium                                                                    |

**Description**

An attacker may inject payloads into processes via Microsoft Office. While legitimate in certain cases, code injection can also be used in malicious ways.

**Attacker's Goals**

* An attacker attempts to gain code execution via a phishing document.
* Attackers may inject code into processes to evade process-based defenses, as well as possibly elevate privileges.

**Investigative actions**

* Check the source of the document (received by mail or loaded locally).
* Check whether the injecting process is benign and if this was a desired behavior as part of its normal execution flow.

</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/microsoft-office-injects-code-into-a-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.
