Illicit OAuth Grant
Also called Consent phishing, Illicit consent grant.
Tricking a user into authorizing a malicious app's access to their account.
What it is
An attack where a user is lured into granting a malicious application standing access to their account or data through a legitimate OAuth consent flow, rather than surrendering their password. The granted token, not a credential, becomes the attacker's access.
Why it matters
Because the access is authorized and token-based, it can survive password resets and multi-factor prompts, so reviewing granted application consents is a distinct and necessary part of cloud identity investigations.
In practice
A responder finds a rogue application with mailbox read consent across several accounts, the real foothold that resetting passwords never removed.
What to look for
- Consent to new apps requesting mail, files or offline access.
- Apps with unfamiliar publishers or reply URLs.
- Data access through app tokens after a password reset.
Common mistake
Resetting the password and calling it fixed. The app's token keeps working until the grant is revoked.
Use it in CyberKit
In the field
Well-known tools where this shows up on the job. They are listed to show the landscape, not as a recommendation.
-
Microsoft Entra ID Protection Commercial
Scores sign-in and user risk in Microsoft Entra ID and can force MFA or a reset.
-
Okta Identity Threat Protection Commercial
Evaluates session risk continuously and can end sessions when it changes.
-
BloodHound Open source
Maps attack paths through Entra ID and Active Directory relationships.
Read next
- Identity Federation: Trusting an external identity provider to authenticate users into the cloud.
- Cloud Persistence: Techniques that let an attacker retain cloud access across sessions.
- Identity and Access Management: The system of identities, roles, and policies that gates access to cloud resources.