Accounts & identity
OAuth token theft
OAuth token theft
OAuth token theft lets an attacker reuse an application's existing authorisation without necessarily knowing the password.
Fiche de sensibilisationPrête à diffuser à vos équipes ou clients
MIGHT YOU BE AFFECTED?
Turn knowledge into action.
How does this work?
OAuth token theft lets an attacker reuse an application's existing authorisation without necessarily knowing the password. Investigation requires examining identity events, sessions and effective permissions; a single alert alone does not establish impact.
REAL-WORLD EXAMPLE
« A compromised app uses a stolen token to read files in a cloud workspace. »
Typical sequence
- 1Obtain an OAuth token from a compromised device, log or app.
- 2Identify its scope and remaining validity.
- 3Present the token to an authorised API or service.
- 4Access data covered by the granted permissions.
- 5Continue requests until the token expires or is revoked.
Warning signs
- Unusual activity in security logs.
- Unknown devices, processes or network origins.
- Unexplained setting or permission changes.
- Correlated security alerts.
- Unauthorised access or data modifications.
How to protect yourself
- Revoke suspicious application grants and rotate exposed bearer tokens.
- Limit privileges and protect accounts.
- Patch software and review configurations.
- Use context-appropriate strong authentication.
- Monitor and investigate suspicious logs.
- Train staff to recognise deceptive requests.
- Keep protected and tested backups.
If you think you are affected
Suspend suspicious access, preserve events and identify misused sessions or permissions. Revoke tokens; limit OAuth scopes; audit authorised applications. Revoke affected sessions and review account changes.
Last updated: 8 October 2026