Session cookie theft
Session cookie theft is the stealing of the token a website sets after you log in. An attacker who holds a valid session cookie can use the account without the password and, depending on the service, without passing multi-factor authentication again, until the session expires or is revoked.
Current as of · Editorial policy
How it works
After you sign in, a website gives your browser a session cookie so that it does not ask for your password on every page. MITRE ATT&CK describes the technique as stealing web session cookies to gain authenticated access without needing credentials, and notes that cookies are often valid for a long time, even if the application is not actively used.
Attackers obtain cookies in several ways: extracting them from disk, browser memory or network traffic, injecting malicious JavaScript into websites, using malicious proxies in phishing campaigns, and deploying malware. MITRE lists infostealers such as Lumma, RedLine and Raccoon among the tools that take cookies from browsers.
How it shows up in executive exposure
A stolen cookie can bypass the password and a previously completed multi-factor step, because the service already considers the session authenticated. That makes it attractive against executives, whose email and cloud accounts are valuable. Cookies are usually captured together with other data in a stealer log.
EDG3, WebThreat's threat intelligence for leaked data, watches the channels where stealer logs, and the cookies inside them, are posted and sold. CEM shows which executives already appear in breach corpora and leak databases. For how a stolen session changes the response to a leak, see combolists vs stealer logs vs database dumps.
How to reduce the risk
MITRE lists these mitigations:
- Use hardware-based multi-factor authentication such as FIDO keys, which include domain information and so resist proxy-based cookie theft.
- Configure browsers to delete persistent cookies regularly and limit cookie lifespan.
- Train users to recognize phishing and avoid running untrusted JavaScript.
- Audit sign-in activity for impossible travel and other anomalies.
- Keep browsers and password managers updated.
- Disable third-party cookies and limit browser extensions.
If a cookie is believed stolen, signing out all sessions and revoking tokens at the service is the direct response.
How it differs from related terms
Stealing a password gives a credential that can be used again and again, while a cookie gives a live session that expires. A credential pair is a username and password. Account takeover is the outcome, and cookie theft is one route to it. An infostealer is the malware that often does the theft.
Frequently asked questions
Does multi-factor authentication stop cookie theft?
Not always. A stolen session cookie can skip the login step. MITRE points to hardware-based multi-factor tokens that bind to the domain as a mitigation against proxy-based theft.
How long does a stolen cookie work?
Until the session expires or is revoked. MITRE notes that cookies are often valid for an extended period.
Sources
- Steal Web Session Cookie (T1539), MITRE ATT&CK, accessed
Related terms
See your leadership's exposure
CEM finds your executives from your company name, checks them against breach corpora and leak databases, and scores each person from 0 to 100.