Consent phishing
Consent phishing
OAuth consent phishing tricks a user into authorising a malicious application that can access data without necessarily stealing the user's password.
MIGHT YOU BE AFFECTED?
Turn knowledge into action.
How does this work?
The attacker presents an appealing app or shared document and directs the victim to a genuine OAuth consent screen. If broad permissions are accepted, the app may read messages, files or other information according to the granted scopes. Successful MFA does not prevent misuse of permissions that the user approves.
REAL-WORLD EXAMPLE
« An employee receives a sharing invitation that asks them to authorise an unknown app to read email and retain offline access. »
Typical sequence
- 1Present an app under a credible identity or pretext.
- 2Direct the user to an OAuth consent prompt.
- 3Request permissions broader than the advertised purpose.
- 4Use the tokens and permissions actually granted.
- 5Maintain access while consent remains valid.
Warning signs
- Requested permissions unrelated to the advertised function.
- Unknown app publisher or unfamiliar application.
- Offline access or broad mailbox read permission.
- Unexpected API activity following authorisation.
- New consent grants outside approved IT procedures.
How to protect yourself
- Reject OAuth consent requests demanding unrelated mailbox or file scopes.
- Limit user consent to approved or verified applications.
- Require administrative approval for sensitive applications.
- Review scopes before granting permission.
- Audit third-party apps and consent grants regularly.
- Monitor high-risk API permissions and activity.
- Use approved internal sharing workflows.
If you think you are affected
Revoke the application's consent and tokens, and determine which permissions and data were accessible. Check audit logs, mailbox rules and similar apps authorised by other accounts. Preserve evidence and follow applicable notification obligations.
Last updated: 8 October 2026