Accounts & identity
Pass-the-cookie
Pass-the-cookie
Pass-the-cookie reuses a captured session cookie to impersonate an already authenticated browser.
Fiche de sensibilisationPrête à diffuser à vos équipes ou clients
MIGHT YOU BE AFFECTED?
Turn knowledge into action.
How does this work?
Pass-the-cookie reuses a captured session cookie to impersonate an already authenticated browser. Investigation requires examining identity events, sessions and effective permissions; a single alert alone does not establish impact.
REAL-WORLD EXAMPLE
« After endpoint infection, a web session appears on a foreign device without a fresh MFA challenge. »
Typical sequence
- 1Compromise an authenticated browser's cookie store.
- 2Extract a still-valid session cookie.
- 3Import it into an attacker-controlled environment.
- 4Make requests before cookie expiry.
- 5Act if session binding controls permit reuse.
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 stolen cookie-backed sessions and secure browser profiles.
- 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. Protect endpoints; limit session lifetime; revoke stolen cookies. Revoke affected sessions and review account changes.
Last updated: 8 October 2026