Session Hijacking
Session hijacking is taking over a user's already-logged-in session by stealing the session cookie or token a website issues after sign-in, which lets an attacker use the account without needing the password or MFA.
Also called: session hijack, cookie theft, session token theft, pass-the-cookie, session replay
What is session hijacking?
After you sign in to a website, it gives your browser a session cookie or token so you don't have to sign in again on every page. Whoever holds that token is treated as you. Session hijacking means stealing it. MITRE ATT&CK notes that a stolen web session cookie can let an attacker into an account without credentials, and can get around multifactor authentication.
How does session hijacking work?
- Infostealer malware copies cookies from the browser on an infected device.
- Adversary-in-the-middle phishing pages sit between the victim and the real site, relaying the login and MFA, then keep the session cookie that's issued.
- Malicious browser extensions read cookies from the browser.
- Insecure connections on old or poorly built sites can expose session tokens on shared networks.
The attacker loads the cookie into their own browser and is immediately logged in as the victim, often to email or cloud apps.
How to protect your business
- Use phishing-resistant MFA such as passkeys, which defeats relay phishing kits.
- Set shorter session lifetimes for sensitive apps and require sign-in again for risky actions.
- Use conditional access that ties sessions to managed, compliant devices.
- Run endpoint protection that detects infostealers.
- After any suspected compromise, revoke all sessions, not just the password.
Related terms
Sources
- Steal Web Session Cookie (T1539) (MITRE ATT&CK)
- Use Alternate Authentication Material: Web Session Cookie (T1550.004) (MITRE ATT&CK)
Drafted with AI assistance, then edited and fact-checked by a person. How we use AI.
