Deployed malware such as YouieLoader capable of capturing victim system browser information.1
Browser Information Discovery T1217
- Tactic
- Discovery
- Platforms
- Linux, macOS, Windows
- Version
- 2.0
- Created
- 18 April 2018
- Last modified
- 12 May 2026
- Contributors
- Mike Kemmerer; Manikantan Srinivasan, NEC Corporation India; Yinon Engelsman, Talon Cyber Security; Yonatan Gotlib, Talon Cyber Security
Adversaries may enumerate information about browsers to learn more about compromised environments. Data saved by browsers (such as bookmarks, accounts, and browsing history) may reveal a variety of personal information about users (e.g., banking sites, relationships/interests, social media, etc.) as well as details about internal network resources such as servers, tools/dashboards, or other related infrastructure.[1]
Browser Information Discovery MITRE reference T1217
7 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 targeted the browsing history of network administrators.1
Retrieves browser histories via infostealer malware such as Raccoon Stealer.1
Has used Google Chrome bookmarks to identify internal resources and assets.1
Has used <code>type \\<hostname>\c$\Users\<username>\Favorites\Links\Bookmarks bar\Imported From IE\*citrix*</code> for bookmark discovery.1
Has collected sensitive browser data using the function GetBrowserData() to include login credentials, bookmarks, cookies, and encryption keys.1
All 7 groups for this technique · 6 newest in this preview
4 campaigns have been recorded using this technique. Listed newest first; dates are year-granularity and attribution is MITRE’s.
During the 3CX Supply Chain Attack, AppleJeus leveraged ICONICSTEALER to steal browser information to include browser history located on the infected host.123
During Juicy Mix, OilRig used the CDumper (Chrome browser) and EDumper (Edge browser) data stealers to collect cookies, browsing history, and credentials.1
During Outer Space, OilRig used a Chrome data dumper named MKG.1
During Operation AkaiRyū, MirrorFace exported Chrome web data including contact information, keywords, autofill data, and stored credit card information.1
All 4 campaigns for this technique
18 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 searched browser data for cookies, history, login databases, and cryptocurrency wallets.1
Has searched the victim device for browser extensions including those commonly associated with cryptocurrency wallets.1234567
Can collect information from browsers and browser extensions.1
Has identified and gathered information from two-factor authentication extensions for multiple browsers.1
Collects information from Chromium-based browsers and Firefox such as cookies, history, downloads, and extensions.12
To collect data on the host's Wi-Fi connection history, LightSpy reads the /Library/Preferences/SystemConfiguration/com.apple.airport.preferences.plist file. It also utilizes Apple's CWWiFiClient API to scan for nearby Wi-Fi networks and obtain data on the SSID, security type, and RSSI (signal strength) values.1
All 18 software entries for this technique · 6 newest in this preview
Offense vs defense T1217
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.
Browser Information Discovery detection strategy DET0013
MITRE names one behaviour worth catching for this technique and breaks it into 3 analytics, one per platform. Each carries the log sources it needs and the fields you tune per environment.
Detection of Local Browser Artifact Access for Reconnaissance
AN0037 · Windows
Access to browser artifact locations (e.g., Chrome, Edge, Firefox) by processes like PowerShell, cmd.exe, or unknown tools, followed by file reads, decoding, or export operations indicating enumeration of bookmarks, autofill, or history databases.
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:Sysmon | EventCode=1 |
| File CreationDC0039 | WinEventLog:Sysmon | EventCode=11 |
| Command ExecutionDC0064 | WinEventLog:PowerShell | EventCode=4103, 4104, 4105, 4106 |
Tunable fields
MITRE calls these the analytic’s mutable elements: the thresholds and filters you set for your own environment.
| Field | What you tune |
|---|---|
| TargetPathRegex | Location of browser data folders like %APPDATA%\Google\Chrome\User Data or %APPDATA%\Mozilla\Firefox |
| ParentProcess | Used to exclude known browser maintenance or backup processes |
| ScriptBlockPattern | Used to detect suspicious PowerShell commands targeting browser data |
AN0038 · Linux
Unauthorized shell or script-based access to browser config or SQLite history files, typically in ~/.config/google-chrome/, ~/.mozilla/, or ~/.var/app folders, indicating enumeration of bookmarks or saved credentials.
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 |
|---|---|---|
| File AccessDC0055 | auditd:SYSCALL | open, read, or stat of browser config files |
| Command ExecutionDC0064 | linux:syslog | Suspicious script or command execution targeting browser folders |
Tunable fields
MITRE calls these the analytic’s mutable elements: the thresholds and filters you set for your own environment.
| Field | What you tune |
|---|---|
| BrowserProfilePath | User-specific browser data folders, e.g., ~/.config/chromium/Default/History |
| ShellRegex | Shell pattern detecting suspicious access to .sqlite or .json files |
AN0039 · macOS
Scripting or CLI tool access to ~/Library/Application Support/Google/Chrome or ~/Library/Safari bookmarks, cookies, or history databases. Detection relies on unexpected processes accessing or reading from these locations.
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 | macos:osquery | process reading browser configuration paths |
| File AccessDC0055 | macos:unifiedlog | Access to ~/Library/*/Safari or Chrome directories by non-browser processes |
Tunable fields
MITRE calls these the analytic’s mutable elements: the thresholds and filters you set for your own environment.
| Field | What you tune |
|---|---|
| BrowserDBPath | System-specific paths to browser databases in user Library folders |
| NonBrowserProcessList | Processes not expected to touch browser DBs (e.g., curl, bash, python) |
Tests from Atomic Red Team (MIT licence) · technique definition