> 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/high-volume-resent-emails-from-various-sources.md).

# High-volume resent emails from various sources

### Synopsis

| Field                | Value                                           |
| -------------------- | ----------------------------------------------- |
| Activation Period    | 14 Days                                         |
| Training Period      | 30 Days                                         |
| Test Period          | 12 Hours                                        |
| Deduplication Period | 1 Day                                           |
| Required Data        | Microsoft 365 Emails                            |
| Detection Modules    | Email                                           |
| Detector Tags        | Phishing                                        |
| ATT\&CK Tactic       | Initial Access (TA0001)                         |
| ATT\&CK Technique    | Phishing: Spearphishing via Service (T1566.003) |
| Severity             | Informational                                   |

### Description

A single free email provider account (identified via Resent-From header) was the source of multiple inbound emails with different From address domains. This pattern may point on a resend/redirect campaign where free email accounts are used to relay emails while preserving original From headers and DKIM signatures.

### Attacker's Goals

* Relay phishing emails through compromised free email accounts to bypass SPF/DKIM/DMARC checks.
* Abuse ARC chain trust to deliver spoofed brand emails as legitimate.
* Trick recipients into clicking malicious links or disclosing credentials.

### Investigative actions

* Examine the Resent-From address and check if it is a known compromised account.
* Review the From domains — are they well-known brands being spoofed?
* Check the ARC chain and authentication results for pass-to-fail degradation.
* Verify whether the emails contain suspicious links, attachments, or hidden text.
* Search for other emails from the same Resent-From address across the organization.

### Variations

<details>

<summary>High-volume resent emails from various sources (massive scale)</summary>

**Synopsis**

| Field             | Value                                           |
| ----------------- | ----------------------------------------------- |
| ATT\&CK Tactic    | Initial Access (TA0001)                         |
| ATT\&CK Technique | Phishing: Spearphishing via Service (T1566.003) |
| Severity          | Low                                             |

**Description**

A large volume of emails from many different From domains was observed, all sharing the same free email provider Resent-From address. This is a strong indicator of a resend/redirect phishing campaign using a compromised free email account.

**Attacker's Goals**

* Relay phishing emails through compromised free email accounts to bypass SPF/DKIM/DMARC checks.
* Abuse ARC chain trust to deliver spoofed brand emails as legitimate.
* Trick recipients into clicking malicious links or disclosing credentials.

**Investigative actions**

* Examine the Resent-From address and check if it is a known compromised account.
* Review the From domains — are they well-known brands being spoofed?
* Check the ARC chain and authentication results for pass-to-fail degradation.
* Verify whether the emails contain suspicious links, attachments, or hidden text.
* Search for other emails from the same Resent-From address across the organization.

</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/high-volume-resent-emails-from-various-sources.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.
