Topic · Threats
Consent phishing
Consent phishing deceives users into granting a malicious application access to account data or actions.
How it works
An attacker presents a plausible OAuth permission screen and obtains approved API scopes without stealing a password.
What can go wrong
Legitimate authentication can succeed while the granted application quietly reads mail or creates persistence.
What to check or do
Restrict third-party app consent and audit grants, publishers and unusual application permissions.
Practical scenario
A user approves an apparently helpful cloud add-in asking to read and send email. The app obtains delegated permissions and continues operating even after the account password is reset.
Verification checklist
- Enumerate OAuth application grants and privileged scopes.
- Identify the publisher, approval source and suspicious API operations.
- Revoke unauthorized grants and active tokens.
- Restrict user consent and alert on new high-risk applications.
How to investigate Consent phishing
- Signal to investigate
- A login workflow grants an unexpected third-party app mailbox permissions.
- Evidence to collect
- Audit OAuth application IDs, scopes, consent events and admin policies.
- Common wrong conclusion
- Resetting a password alone may not revoke already granted application permissions.
Put this into practice
Run a focused check, then explore protection if your domain needs it.