Session hijacking
Session hijacking
Session theft reuses an authenticated context, sometimes through a stolen token or cookie, without repeating the original login.
MIGHT YOU BE AFFECTED?
Turn knowledge into action.
How does this work?
An active session represents a previous successful authentication. An actor who obtains its identifier or controls its browser context may act with the victim's permissions until expiry or revocation. Session hijacking describes abuse of that session; cookie theft is only one possible route. MFA at sign-in cannot by itself prevent reuse of an already established session.
REAL-WORLD EXAMPLE
« A manager's account shows unfamiliar access followed by file exports. Responders check devices, revoke sessions and investigate what was accessed. »
Typical sequence
- 1Access an authenticated device or browsing context.
- 2Capture a token, cookie or other session artifact.
- 3Transfer it to an attacker-controlled environment.
- 4Present it to the service before expiration or revocation.
- 5Perform actions through the impersonated session.
Warning signs
- Activity at unusual times or from unknown devices.
- Rapid access from inconsistent environments.
- Sensitive actions without recent authentication.
- Unrecognised security changes or data exports.
- Browser, identity or endpoint compromise signals.
How to protect yourself
- Revoke sessions reused from unknown devices without a new login.
- Use short-lived, revocable sessions.
- Enforce conditional access and device checks.
- Use phishing-resistant MFA and reauthentication for critical actions.
- Log sessions, security changes and sensitive data access.
- Keep browsers and endpoints patched.
- Reduce standing account privileges.
If you think you are affected
Stop suspicious activity, preserve relevant logs and messages, revoke affected sessions or credentials, investigate changes and report confirmed exposure to the appropriate team.
Last updated: 8 October 2026