Has used custom malware to steal login and cookie data from common browsers.1
Steal Web Session Cookie T1539
- Tactic
- Credential Access
- Platforms
- Linux, macOS, Office Suite, SaaS, Windows
- Version
- 1.5
- Created
- 08 October 2019
- Last modified
- 12 May 2026
- Contributors
- Microsoft Threat Intelligence Center (MSTIC); Johann Rehberger; Menachem Goldstein; Don Le, Stifel Financial
An adversary may steal web application or service session cookies and use them to gain access to web applications or Internet services as an authenticated user without needing credentials. Web applications and services often use session cookies as an authentication token after a user has authenticated to a website.
Steal Web Session Cookie MITRE reference T1539
8 groups have been recorded using this technique. Newest first; each entry carries MITRE’s procedure text and a link to the group’s full record. Click a name to filter the rules below.
Has used EvilGinx to steal the session cookies of victims directed to phishing domains.1
Retrieves browser cookies via Raccoon Stealer.1
Has used an unnamed post-exploitation tool to steal cookies from the Chrome browser.1
Can steal cookies and session information from browsers.1
Has used malware, such as TRANSLATEXT, to steal and exfiltrate browser cookies.12
All 8 groups for this technique · 6 newest in this preview
1 campaign has been recorded using this technique. Listed newest first; dates are year-granularity and attribution is MITRE’s.
During the SolarWinds Compromise, APT29 stole Chrome browser cookies by copying the Chrome profile directories of targeted users.1
All 1 campaigns for this technique
20 software entries are documented implementing this technique. MITRE files each as a tool or as malware; newest first, then by how many groups carry them.
Has captured session cookies and related session artifacts when the interacted phishing lure acts as proxy for legitimate requests with login services.12
Can list the contents of %LocalAppData%\Google\Chrome\User Data\ and %LocalAppData%\Microsoft\Edge\User Data\ to obtain cookies.1
Has harvested Safari cookies stored within /Library/Containers/com.apple.Safari/Data/Library/Cookies/ Cookies.binarycookies.1 GlassWorm has also stolen cookies within Chromium and Firefox browsers.21
Can collect information on each session with a victim including the session cookie.12
All 20 software entries for this technique · 6 newest in this preview
Offense vs defense T1539
Is defensive coverage keeping up with adversary use? Eight counts, each ranked against all 697 ATT&CK techniques. Attack sits left, defense right, so a shape leaning left means adversaries are better documented here than defenders are equipped. Hover any spoke for its percentile and the share of techniques that have more. The timeline below shows when each side arrived.
How it got here
Adversary activity (campaign spans) over cumulative rule output. Each source is plotted independently from zero, so neither line includes the other. Campaign dates are year-granularity.
Steal Web Session Cookie detection strategy DET0509
MITRE names one behaviour worth catching for this technique and breaks it into 5 analytics, one per platform. Each carries the log sources it needs and the fields you tune per environment.
Detection of Web Session Cookie Theft via File, Memory, and Network Artifacts
AN1402 · Windows
Detects suspicious access to browser session cookie storage (e.g., Chrome’s Cookies SQLite DB) or memory reads of browser processes. Anomalous injection or memory dump utilities targeting browser processes such as chrome.exe, firefox.exe, or msedge.exe.
Log sources
The data this analytic draws on. You do not need every component — each one you already collect covers part of it. Each links to its ATT&CK record.
| Data component | Name | Channel |
|---|---|---|
| Process CreationDC0032 | WinEventLog:Security | EventCode=4688 |
| Process AccessDC0035 | WinEventLog:Sysmon | EventCode=10 |
| File ModificationDC0061 | WinEventLog:Sysmon | EventCode=2 |
Tunable fields
MITRE calls these the analytic’s mutable elements: the thresholds and filters you set for your own environment.
| Field | What you tune |
|---|---|
| TargetProcessList | Monitored browsers (e.g., chrome.exe, firefox.exe) |
| AccessToolList | Suspicious tools used for injection or memory access (e.g., mimikatz, procdump) |
| TargetCookiePaths | Locations of cookie stores like AppData\Local\Google\Chrome\User Data\Default\Cookies |
AN1403 · Linux
Detects access to known browser cookie files (e.g., ~/.mozilla/firefox/*.default/cookies.sqlite, ~/.config/google-chrome/) and suspicious reads of browser memory via /proc/[pid]/mem or ptrace.
Log sources
The data this analytic draws on. You do not need every component — each one you already collect covers part of it. Each links to its ATT&CK record.
| Data component | Name | Channel |
|---|---|---|
| Process AccessDC0035 | auditd:SYSCALL | ptrace syscall or access to /proc/*/mem |
| File AccessDC0055 | auditd:SYSCALL | open or read to browser cookie storage |
Tunable fields
MITRE calls these the analytic’s mutable elements: the thresholds and filters you set for your own environment.
| Field | What you tune |
|---|---|
| CookieFilePatterns | Regex paths to known browser cookie locations |
| TimeWindow | Correlated time range between cookie read and web upload or process injection |
| BrowserProcPatterns | Expected names for browser processes being accessed |
AN1404 · macOS
Detects unauthorized access to browser cookie paths (e.g., ~/Library/Application Support/Google/Chrome/Default/Cookies) or task_for_pid/vm_read calls to Safari/Chrome memory space.
Log sources
The data this analytic draws on. You do not need every component — each one you already collect covers part of it. Each links to its ATT&CK record.
| Data component | Name | Channel |
|---|---|---|
| Process AccessDC0035 | macos:unifiedlog | vm_read, task_for_pid, or file open to cookie databases |
| File AccessDC0055 | fs:fsusage | file open for known browser cookie paths |
Tunable fields
MITRE calls these the analytic’s mutable elements: the thresholds and filters you set for your own environment.
| Field | What you tune |
|---|---|
| TargetBrowserList | List of processes considered web browsers on macOS |
| BrowserCookiePathList | Cookie database paths specific to each browser |
AN1405 · Office Suite
Detects automation macros or VBA scripts in documents that access browser file paths, read cookie data, or attempt to exfiltrate browser session tokens over HTTP.
Log sources
The data this analytic draws on. You do not need every component — each one you already collect covers part of it. Each links to its ATT&CK record.
| Data component | Name | Channel |
|---|---|---|
| Application Log ContentDC0038 | m365:unified | RunMacro |
| File ModificationDC0061 | WinEventLog:Sysmon | EventCode=2 |
Tunable fields
MITRE calls these the analytic’s mutable elements: the thresholds and filters you set for your own environment.
| Field | What you tune |
|---|---|
| MacroTargetPath | Files or directories macros are attempting to access |
| HTTPDestinationIPList | List of IPs or domains that are uncommon for macro-based HTTP POSTs |
AN1406 · SaaS
Detects use of session cookies or authentication tokens from unusual user agents or locations. Identifies token reuse without reauthentication or attempts to bypass MFA using previously stolen cookies.
Log sources
The data this analytic draws on. You do not need every component — each one you already collect covers part of it. Each links to its ATT&CK record.
| Data component | Name | Channel |
|---|---|---|
| User Account AuthenticationDC0002 | saas:googleworkspace | login with reused session token and mismatched user agent or IP |
| Logon Session CreationDC0067 | saas:okta | session.token.reuse |
Tunable fields
MITRE calls these the analytic’s mutable elements: the thresholds and filters you set for your own environment.
| Field | What you tune |
|---|---|
| TokenReuseTimeWindow | Max allowed delta between token issuance and second use |
| UserAgentAnomalyScore | Deviation score from normal browser/device fingerprint |
| GeoLocationAnomalyScore | Deviation in IP region or ASN per user profile |
Implement auditing for authentication activities and user logins to detect the use of stolen session cookies. Monitor for impossible travel scenarios and anomalous behavior that could indicate the use of compromised session tokens or cookies.
Deploy hardware-based token (e.g., YubiKey or FIDO key), which incorporates the target login domain as part of the negotiation protocol, will prevent session cookie theft through proxy methods. Implement Conditional Access policies to only allow logins from trusted devices, such as those enrolled in Intune or joined via Hybrid/Entra. This mitigates the risk of session cookie replay attacks by ensuring that stolen tokens cannot be reused on unauthorized devices.
Restrict or block web-based content that could be used to extract session cookies or credentials stored in browsers. Use browser security settings, such as disabling third-party cookies and restricting browser extensions, to limit the attack surface.
Configure browsers or tasks to regularly delete persistent cookies. Additionally, minimize the length of time a web cookie is viable to potentially reduce the impact of stolen cookies while also increasing the needed frequency of cookie theft attempts – providing defenders with additional chances at detection. For example, use non-persistent cookies to limit the duration a session ID will remain on the web client cache where an attacker could obtain it.
Regularly update web browsers, password managers, and all related software to the latest versions. Keeping software up-to-date reduces the risk of vulnerabilities being exploited by attackers to extract stored credentials or session cookies.
Train users to identify aspects of phishing attempts where they're asked to enter credentials into a site that has the incorrect domain for the application they are logging into. Additionally, train users not to run untrusted JavaScript in their browser, such as by copying and pasting code or dragging and dropping bookmarklets.
Tests from Atomic Red Team (MIT licence) · technique definition