Skip to content
StrikeCyberStrikeCyber
Field Manual · Attack technique

Session Hijacking and Token Theft

Reviewed November 13, 2026Attack technique 1 min read

Quick answer

Session hijacking is when an attacker steals the token or cookie that proves you have already signed in, then uses it to act as you without needing your password or MFA. Token theft is now the main way attackers get past multi-factor authentication, because MFA protects the sign-in, not the session that follows.

On this page
01

How It Works

After you sign in, the application issues a session cookie or access token that your browser presents with every request. Attackers obtain it in three main ways: an adversary-in-the-middle phishing page that relays your real sign-in and captures the resulting cookie; infostealer malware that copies cookies from the browser; and application flaws such as cross-site scripting or tokens leaked in URLs and logs. In cloud environments, refresh tokens and OAuth grants can keep access alive for days or months, even after a password change.

02

Why It Matters

A stolen session looks like the legitimate user, often from a plausible location. Without device binding or token protection, the attacker inherits whatever the user could do: read email, approve payments, download files or register new MFA methods to keep access permanently.

03

How to Test for It

  1. Test whether a captured session cookie or token can be replayed from a different device, browser and network.
  2. Check session lifetimes, idle timeouts and whether sign-out and password resets revoke active sessions and refresh tokens.
  3. Run an authorized adversary-in-the-middle phishing simulation to measure whether your MFA can be relayed.
  4. Test web applications for cross-site scripting, tokens in URLs and cookies missing Secure, HttpOnly and SameSite flags.
  5. Review OAuth consent and app registrations for over-privileged grants that act as long-lived tokens.
04

How to Reduce the Risk

Use phishing-resistant MFA such as passkeys or FIDO2 keys, which cannot be relayed by a proxy; require managed and compliant devices for sensitive apps; enable token protection and continuous access evaluation where your identity provider supports them; keep sessions short for high-risk applications; revoke sessions on password reset and on risk signals; and harden application cookies.

05

Regulatory and Framework Context

In the US, CISA's guidance on phishing-resistant MFA and OMB's zero trust memorandum both target session theft, and federal agencies are required to adopt phishing-resistant authentication.

Latest intel on this topic

Updated hourly from the daily briefing. More in phishing campaigns and alerts.

Common questions

Does changing my password stop a session hijack?

Not always. Many services keep existing sessions and refresh tokens alive after a password change. You must also revoke sessions and tokens explicitly.

Which MFA methods resist token theft?

Passkeys and FIDO2 security keys are bound to the real website, so a phishing proxy cannot complete the sign-in. Push approvals, SMS codes and authenticator codes can all be relayed.

For testers: finding write-ups

How this shows up in a penetration test report, with severity, verification and remediation, in the StrikeOps Findings Library.

Change log

  1. November 13, 2026First published.
(877) 657-8496