Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
mukul975 avatar

Detecting Suspicious Oauth Application Consent

  • 1 installs
  • 27.3k repo stars
  • Updated August 2, 2026
  • mukul975/anthropic-cybersecurity-skills

Detect risky OAuth consent grants in Azure AD / Entra ID using Microsoft Graph API, audit logs, and permission analysis to catch illicit-consent attacks.

About

Detects suspicious OAuth application consent grants in Azure AD / Microsoft Entra ID using Microsoft Graph, audit logs, and permission analysis. A security team uses it to identify illicit consent grant attacks and risky application permissions.

  • Microsoft Graph and audit-log analysis of consent grants
  • Flags illicit-consent and over-permissioned applications

Detecting Suspicious Oauth Application Consent by the numbers

  • 1 all-time installs (skills.sh)
  • Ranked #1,835 of 2,203 Security skills by installs in the Skillselion catalog
  • Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/mukul975/anthropic-cybersecurity-skills --skill detecting-suspicious-oauth-application-consent

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs1
repo stars27.3k
Last updatedAugust 2, 2026
Repositorymukul975/anthropic-cybersecurity-skills

What it does

Detect risky OAuth consent grants in Azure AD / Entra ID using Microsoft Graph API, audit logs, and permission analysis to catch illicit-consent attacks.

Files

SKILL.mdMarkdownGitHub ↗

Detecting Suspicious OAuth Application Consent

Overview

Illicit consent grant attacks trick users into granting excessive permissions to malicious OAuth applications in Azure AD / Microsoft Entra ID. This skill uses the Microsoft Graph API to enumerate OAuth2 permission grants, analyze application permissions for overly broad scopes, review directory audit logs for consent events, and flag high-risk applications based on publisher verification status and permission scope.

When to Use

  • When investigating security incidents that require detecting suspicious oauth application consent
  • When building detection rules or threat hunting queries for this domain
  • When SOC analysts need structured procedures for this analysis type
  • When validating security monitoring coverage for related attack techniques

Prerequisites

  • Azure AD / Entra ID tenant with Global Reader or Security Reader role
  • Microsoft Graph API access with Application.Read.All, AuditLog.Read.All, Directory.Read.All
  • Python 3.9+ with msal, requests
  • App registration with client secret or certificate for authentication

Steps

1. Authenticate to Microsoft Graph using MSAL client credentials flow 2. Enumerate all OAuth2 permission grants via /oauth2PermissionGrants 3. List service principals and their assigned application permissions 4. Query directory audit logs for Consent to application events 5. Flag applications with high-risk scopes (Mail.Read, Files.ReadWrite.All, etc.) 6. Check publisher verification status for each application 7. Generate risk report with remediation recommendations

Expected Output

  • JSON report listing all OAuth apps with granted permissions, risk scores, unverified publishers, and suspicious consent patterns
  • Audit trail of consent grant events with user and IP details

Related skills

Securityauditappsec

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.