> 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/single-ip-accessed-mail-items-of-multiple-users.md).

# Single IP accessed mail items of multiple users

### Synopsis

| Field                | Value                                                 |
| -------------------- | ----------------------------------------------------- |
| Activation Period    | 14 Days                                               |
| Training Period      | 30 Days                                               |
| Test Period          | 1 Hour                                                |
| Deduplication Period | 1 Day                                                 |
| Required Data        | Office 365 Audit                                      |
| Detection Modules    | Identity Threat Module, Email                         |
| Detector Tags        | Extortion                                             |
| ATT\&CK Tactic       | Collection (TA0009)                                   |
| ATT\&CK Technique    | Email Collection: Remote Email Collection (T1114.002) |
| Severity             | Informational                                         |

### Description

A single caller IP accessed Exchange mail items belonging to multiple distinct users within a short time window. This pattern indicates mailbox harvesting from a shared attacker vantage point (VPS or AiTM box).

### Attacker's Goals

An adversary may use a single IP address to access mail items across multiple user accounts, which can aid in the centralized collection and bulk exfiltration of organizational email data.

### Investigative actions

* Pivot on the caller IP across all SaaS audit logs and review every session originated from it.
* For each impacted user, look for fresh OAuth grants, new inbox rules, MFA enrolment changes and anomalous logins.
* Check the IP reputation in SPUR/threat-intel and revoke active sessions for the affected users.

### Variations

<details>

<summary>Single IP accessed mail items of multiple users with suspicious characteristics</summary>

**Synopsis**

| Field             | Value                                                 |
| ----------------- | ----------------------------------------------------- |
| ATT\&CK Tactic    | Collection (TA0009)                                   |
| ATT\&CK Technique | Email Collection: Remote Email Collection (T1114.002) |
| Severity          | Low                                                   |

**Description**

A single caller IP accessed Exchange mail items belonging to multiple distinct users within a short window, and the IP address contributed additional suspicious characteristics (e.g., unmanaged or risky caller IP, anomalous country or ASN for these users).

**Attacker's Goals**

An adversary may use a single IP address to access mail items across multiple user accounts, which can aid in the centralized collection and bulk exfiltration of organizational email data.

**Investigative actions**

* Pivot on the caller IP across all SaaS audit logs and review every session originated from it.
* For each impacted user, look for fresh OAuth grants, new inbox rules, MFA enrolment changes and anomalous logins.
* Check the IP reputation in SPUR/threat-intel and revoke active sessions for the affected users.

</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/single-ip-accessed-mail-items-of-multiple-users.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.