What Is a Web Session?
Before we explain session hijacking, it helps to understand what a “session” is. Every time you log in to a website — your email, your bank, a cloud application — the server creates a session. That session is a temporary trust relationship between your browser and the server.
Instead of asking you to re-enter your password on every single page you click, the server gives your browser a small piece of data called a session token (usually stored as a cookie). Your browser sends that token with every request, and the server uses it to confirm: “Yes, this person has already authenticated — let them through.”
Think of it like a wristband at a concert. You show your ticket (password + MFA) at the gate, and they give you a wristband. After that, you just flash the wristband to get into any area — nobody checks your ticket again.
What Is Session Hijacking?
Session hijacking is when an attacker steals, intercepts, or forges your session token — your “wristband” — and uses it to impersonate you. Once they have your session cookie, they can access your account as if they were you, without ever needing your password or MFA code.
This is what makes session hijacking so dangerous: it happens after authentication. You’ve done everything right — used a strong password, enabled MFA — and the attacker simply bypasses all of it by stealing the token that proves you’re logged in.
MFA protects the login step — it verifies your identity when you first sign in. But once you’re authenticated and a session token is issued, MFA has done its job. If an attacker steals the session token after MFA has been completed, they don’t need to pass MFA again — the token already represents a fully authenticated session.
Types of Session Hijacking Attacks
Attackers use several methods to steal or forge session tokens. Here are the most common techniques that Melbourne businesses should be aware of:
The most common method today. Malware installed on a user’s device (through a phishing email, a fake software download, or a compromised website) silently extracts all browser cookies — including active session tokens — and sends them to the attacker. The user never notices anything unusual.
An attacker injects malicious JavaScript into a vulnerable website. When you visit that page, the script runs in your browser and sends your session cookie to the attacker. This exploits a vulnerability in the website, not in your computer.
On unencrypted or poorly secured networks (like public WiFi at a café), an attacker can intercept network traffic and extract session cookies as they travel between your browser and the server. This is why HTTPS everywhere matters.
The attacker sets a known session ID before you log in (through a crafted URL or hidden form), then waits for you to authenticate. Because the session ID is one the attacker already knows, they can use it immediately after you log in.
A sophisticated phishing technique where the attacker sets up a proxy server between you and the real login page. You enter your credentials and MFA code into what looks like the real site, the proxy passes them through, and the attacker captures the session cookie that comes back — MFA included.
Watch: Session Hijacking Explained
We put together a short video walkthrough explaining session hijacking, how it works in practice, and what it looks like from an attacker’s perspective.
Real-World Example: The 2023 Okta Breach
Session hijacking isn’t a theoretical risk — it’s being used in major attacks right now. One of the most significant recent examples is the 2023 Okta breach.
Okta, a major identity and access management provider, was breached when attackers gained access to its customer support system. Support engineers had been asking customers to upload HAR files (HTTP Archive files used for troubleshooting) which contained active session cookies.
The attackers extracted those session tokens from the uploaded HAR files and used them to access customer accounts — without needing any passwords or MFA codes. The breach affected at least 134 Okta customers, including major security companies like 1Password, BeyondTrust, and Cloudflare.
The Okta breach shows that session hijacking doesn’t just target end users. It can compromise entire identity platforms. If your business uses any cloud-based identity provider (Microsoft Entra ID, Okta, Google Workspace), you’re relying on session security at every level of the chain.
The Scale of Session Cookie Theft
Session hijacking via cookie theft has become an industrial-scale problem:
Infostealer malware — the primary tool used to harvest session cookies — has seen explosive growth. These malware families (Redline, Raccoon, Vidar, Lumma) are sold as a service on criminal marketplaces for as little as $200/month, making session cookie theft accessible to even unsophisticated attackers.
How to Protect Your Business
Session hijacking can’t be stopped by a single control. It requires a layered approach across your devices, your network, and your cloud applications:
All web applications and internal systems should use HTTPS with valid certificates. This prevents session sidejacking on the network. For businesses using Microsoft 365, this is handled automatically — but on-premises applications and custom web apps often still run on HTTP.
Modern EDR solutions detect and block infostealer malware before it can extract browser cookies. This is your front line of defence against the most common session hijacking vector. At Melbit Services, we deploy Microsoft Defender for Endpoint across all managed devices as standard.
Microsoft Entra (Azure AD) Conditional Access policies can require that sessions come from compliant, managed devices. If an attacker tries to replay a stolen session cookie from an unmanaged device, Conditional Access blocks the request — even though the token is technically valid.
The longer a session token is valid, the larger the window for an attacker to steal and use it. Configure your cloud applications to enforce reasonable session timeouts — particularly for privileged accounts. “Stay signed in” options on shared or unmanaged devices are a significant risk.
Token binding ties a session token to the specific device that created it. If an attacker steals the token and tries to use it from a different device, the server rejects it. Microsoft is progressively rolling out token protection for Entra ID sessions.
Many infostealer infections start with a phishing email or a fake software download. Regular security awareness training that covers these vectors — combined with application control policies that prevent unapproved software installation — significantly reduces the risk.
Frequently Asked Questions
Can session hijacking happen on mobile devices?
Yes. Mobile browsers use session cookies just like desktop browsers, and mobile devices can be infected with infostealer malware through malicious apps or phishing links. If your staff use mobile devices for work email or cloud applications, those sessions are just as vulnerable.
Does using a VPN prevent session hijacking?
A VPN encrypts your network traffic, which helps prevent session sidejacking on public WiFi. However, it does not protect against infostealer malware, XSS attacks, or adversary-in-the-middle phishing — which are the most common hijacking methods today. A VPN is one layer, not a complete solution.
How do I know if my session has been hijacked?
Signs include unexpected logouts, sign-ins from unfamiliar locations or devices (visible in your Microsoft 365 sign-in logs or Google account activity), and changes you didn’t make. If you suspect a compromised session, revoke all sessions immediately and change your password.
Is session hijacking the same as credential theft?
No. Credential theft involves stealing your username and password. Session hijacking bypasses credentials entirely by stealing the session token that was issued after you authenticated. This is why MFA stops credential theft but doesn’t stop session hijacking.
What should I do if I think my business has been affected?
Immediately revoke all active sessions for affected accounts, force a password reset, review sign-in logs for suspicious activity, and run a full endpoint scan for infostealer malware. If you need help, contact Melbit Services — we can investigate and remediate quickly.