CyberKit

Session Hijacking

Taking over an already-authenticated session via its token.

What it is

The takeover of a valid, already-authenticated session by obtaining its session identifier or token (through theft, prediction, or interception), and using it to act as the legitimate user. It targets the live session rather than the login credentials.

Why it matters

It bypasses authentication entirely because the session is already trusted, so MFA at login provides no protection once a session is in flight. Short session lifetimes, token binding, and re-authentication for sensitive actions limit the impact.

In practice

An attacker captures a session identifier over an insecure channel and resumes the victim's authenticated web session without ever logging in.

What to look for

  • One session ID used from two locations at once.
  • Session activity after logout or password reset.
  • Session tokens in URLs, logs or referrer headers.

Common mistake

Not tying sessions to anything. Bind tokens to device or client where possible and revoke on risk.

Practice it nearby

CyberKit has no tool for this term itself. These are the closest places to practice it.

In the field

Well-known tools where this shows up on the job. They are listed to show the landscape, not as a recommendation.

  • Burp Suite Commercial

    An intercepting proxy for testing web apps by hand and with its scanner.

  • ZAP Open source

    An open source web app scanner and proxy, often run in CI pipelines.

  • Cloudflare WAF Commercial

    Blocks common web attacks at the edge while the code gets fixed.

Read next

Sources