Favicon cache supercookie (F-CACHE)
A site encodes an ID into which favicons were cached, which survives clearing cookies.
In one line
Can try to tag your browser with a hidden icon cache ID, though fixes limit it
A site encodes an ID into which favicons were cached, which survives clearing cookies.
NDSS 2021 (Solomos et al.) showed a persistent ID stored in the favicon cache across subdomains, surviving cookie clearing and even private browsing in some browsers. Vendors patched after disclosure.
What it can and can't do
What the user does: Nothing. It happens when you visit a site that tries it
It can
- Store an ID using which tiny site icons your browser has cached
- Recognise a returning visitor, even after you clear cookies in unpatched browsers
- Link visits across subdomains of the same site in older versions
It cannot
- Work in browsers that fixed it after researchers reported it in 2021
- Follow you across unrelated sites
- Survive clearing browsing data in updated browsers
How it differs between platforms: Browser makers patched it after 2021, so behavior differs by version.
Browser support
| Browser | Status | First version | Released | Note |
|---|---|---|---|---|
| Chrome | Removed | 1 | 2008-12-11 | Fixed after 2021 disclosure (versions not verified) |
| Edge | Removed | 79 | 2020-01-15 | Fixed after 2021 disclosure (versions not verified) |
| Firefox | Removed | 1 | 2004-11-09 | Fixed after 2021 disclosure (versions not verified) |
| Safari | Removed | 1 | 2003-06-23 | Fixed after 2021 disclosure (versions not verified) |
| Safari on iPhone | Removed | 1 | 2007-06-29 | Fixed after 2021 disclosure (versions not verified) |
| Chrome on Android | Removed | 1 | Not listed | Fixed after 2021 disclosure (versions not verified) |
| Samsung Internet | Removed | 5.0 | 2016-12-15 | Fixed after 2021 disclosure (versions not verified) |
How a site asks for it
| API | Favicon requests to N subdomain paths; navigation redirect probing |
| How access is granted | none |
| What the user sees | Not listed |
| Needs a secure context (HTTPS) | No |
| Needs a user gesture | No |
| How long it lasts | Not listed |
| How to take it back | Not listed |
| Inside an iframe | Not listed |
Typical flow
- Load pages with chosen favicons to write bits
- Probe which favicons are cached
- Reassemble the ID
Data you get
What comes back: 32 bits demonstrated
Shape: integer
| Field | Type | Unit | Range | Precision |
|---|---|---|---|---|
id bits | integer | bits | 32 | needs up to 4 seconds |
Technical limits
- Patched in Chrome, Safari and Brave (reported)
- Needs many subdomains and requests
The story
What it is
A site hides an ID in which tiny page icons your browser has saved.
For you
You never see it. You clear cookies and history, and a site still knows it is you, because of the pattern of tiny icons your browser saved. Browsers have worked to close this.
For makers
Researchers showed it works across subdomains and even in private mode. A tracker could use it as a persistent ID. Makers who care about privacy prefer to avoid it, and browsers are closing the hole.
Where you see it
| Type | Example | Apps |
|---|---|---|
| ads | A tracking network sets a pattern of favicons on a first visit and reads it back later to recognize you. | None named |
| analytics | A measurement script reconnects returning visitors who cleared cookies. | None named |
| security | A fraud tool uses it to link accounts from one browser even in private windows. | None named |
| shopping | A marketing site recognizes a shopper who tries to look anonymous. | None named |
| games | A game site could link a banned user to a new account made in the same browser. | None named |
| media | A publisher could count one reader as one person across paywall resets. | None named |
Risks
- Survives cookie clearing
- Works in private mode
Good uses and abuse
Legitimate uses
- None
Known abuse
- Cookie-free persistent tracking, survives incognito in affected builds
Scores
| Score | Value | Meaning |
|---|---|---|
| Sensitivity | 3 of 5 | How revealing the data is |
| Utility | 1 of 5 | How useful it is to honest apps |
| Friction | 0 of 5 | How much the user has to do |
| Fingerprint bits | 4 | Rough identifying entropy, when known |
History
- 2021-02, paper: Solomos et al. Tracking You Persistently via Favicons (NDSS 2021)
Related capabilities
Related
- ETag and HTTP cache supercookie. Can try to tag your browser with a hidden cached ID, though browsers now limit it
Sources
How well checked: Based on official documentation.