> 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/unusual-display-name-in-from-header.md).

# Unusual display name in From header

### Synopsis

| Field                | Value                                              |
| -------------------- | -------------------------------------------------- |
| Activation Period    | 14 Days                                            |
| Training Period      | 30 Days                                            |
| Test Period          | N/A (single event)                                 |
| Deduplication Period | 1 Day                                              |
| Required Data        | Microsoft 365 Emails                               |
| Detection Modules    | Email                                              |
| ATT\&CK Tactic       | Reconnaissance (TA0043), Initial Access (TA0001)   |
| ATT\&CK Technique    | Phishing for Information (T1598), Phishing (T1566) |
| Severity             | Informational                                      |

### Description

An email was detected with an unusual display name in the From header.

### Attacker's Goals

Evade defenses and hide potential malicious data inside the email display name.

### Investigative actions

* Analyze the email further to determine the source of the anomaly and what can be done about it.

### Variations

<details>

<summary>Unusual display name in the From header containing an embedded URL</summary>

**Synopsis**

| Field             | Value                                              |
| ----------------- | -------------------------------------------------- |
| ATT\&CK Tactic    | Reconnaissance (TA0043), Initial Access (TA0001)   |
| ATT\&CK Technique | Phishing for Information (T1598), Phishing (T1566) |
| Severity          | Low                                                |

**Description**

An email was detected with an unusual sender display name in the From header containing an embedded URL.

**Attacker's Goals**

Evade defenses and hide potential malicious data inside the email display name.

**Investigative actions**

* Analyze the email further to determine the source of the anomaly and what can be done about it.

</details>

<details>

<summary>Unusual display name in the From header that is identical to the email address</summary>

**Synopsis**

| Field             | Value                                              |
| ----------------- | -------------------------------------------------- |
| ATT\&CK Tactic    | Reconnaissance (TA0043), Initial Access (TA0001)   |
| ATT\&CK Technique | Phishing for Information (T1598), Phishing (T1566) |
| Severity          | Informational                                      |

**Description**

An email was detected where the display name in the From header is unusual and matches the sender email address.

**Attacker's Goals**

Evade defenses and hide potential malicious data inside the email display name.

**Investigative actions**

* Analyze the email further to determine the source of the anomaly and what can be done about it.

</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/unusual-display-name-in-from-header.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.
