> 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/possible-consentfix-oauth-token-theft-detected.md).

# Possible ConsentFix - OAuth Token Theft Detected

### Synopsis

| Field                | Value                                                                                                |
| -------------------- | ---------------------------------------------------------------------------------------------------- |
| Activation Period    | 14 Days                                                                                              |
| Training Period      | 30 Days                                                                                              |
| Test Period          | 1 Hour                                                                                               |
| Deduplication Period | 1 Day                                                                                                |
| Required Data        | AzureAD                                                                                              |
| Detection Modules    | Identity Threat Module, SaaS Threat Detection                                                        |
| ATT\&CK Tactic       | Initial Access (TA0001), Credential Access (TA0006), Execution (TA0002)                              |
| ATT\&CK Technique    | Phishing (T1566), User Execution: Malicious Link (T1204.001), Steal Application Access Token (T1528) |
| Severity             | Informational                                                                                        |

### Description

Detection of potential OAuth token theft via a forced 'localhost' redirect and first-party app abuse. This indicates an attacker has likely bypassed MFA to hijack a user's cloud session.

### Attacker's Goals

Bypass identity trust controls to gain persistent unauthorized access to cloud resources.

### Investigative actions

* Check for successful logins to Azure CLI or PowerShell from anomalous IPs.
* Review sign-in logs for User-Agents associated with CLI tools or scripts.
* Revoke all active OAuth refresh tokens for the user immediately.

### Variations

<details>

<summary>OAuth Token Theft - Potential Session Hijacking Detected from new ASN</summary>

**Synopsis**

| Field             | Value                                                                                                |
| ----------------- | ---------------------------------------------------------------------------------------------------- |
| ATT\&CK Tactic    | Initial Access (TA0001), Credential Access (TA0006), Execution (TA0002)                              |
| ATT\&CK Technique | Phishing (T1566), User Execution: Malicious Link (T1204.001), Steal Application Access Token (T1528) |
| Severity          | Low                                                                                                  |

**Description**

Detection of potential OAuth token theft via a forced 'localhost' redirect and first-party app abuse. This indicates an attacker has likely bypassed MFA to hijack a user's cloud session.

**Attacker's Goals**

Bypass identity trust controls to gain persistent unauthorized access to cloud resources.

**Investigative actions**

* Check for successful logins to Azure CLI or PowerShell from anomalous IPs.
* Review sign-in logs for User-Agents associated with CLI tools or scripts.
* Revoke all active OAuth refresh tokens for the user immediately.

</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/possible-consentfix-oauth-token-theft-detected.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.