FROST: A Browser-Only Side Channel That Reads Your SSD to Guess What You're Doing

A browser tab. No prompt, no extension, no native code. That is all a new side-channel attack out of Graz University of Technology needs to tell which websites a victim visits and which applications they launch.

The technique is called FROST. It works by measuring timing variations caused by contention on the target's SSD while a malicious page sits idle in a tab. The drive becomes the sensor. The browser becomes the listener.

Graz has a long bench in this space. The same group produced foundational work on Spectre, Meltdown, and a string of microarchitectural and storage-timing attacks that have repeatedly forced browser vendors to clamp down on high-resolution timers and shared resources. FROST sits in that lineage, but pushes it past CPU caches and into the storage stack.

The mechanics are straightforward in concept. Disk I/O from other processes — the operating system, background apps, the user's own browsing — creates measurable delays in operations the JavaScript code performs against the SSD through ordinary web APIs. The pattern of those delays is distinctive. Loading Gmail looks different from loading a banking portal. Opening Slack looks different from opening a PDF viewer. Train a classifier on the fingerprints and the page can guess what is happening on the machine with high confidence.

What makes FROST notable is the threat model. No malware. No phishing. No permission dialog. The victim only has to leave a tab open.

That covers a lot of behaviour. Background tabs, abandoned news sites, ad iframes, embedded widgets. Any of them, if attacker-controlled, could quietly profile activity on the device for as long as the page remains loaded.

The researchers say the attack works across major browsers and across SSDs from multiple vendors. Hard drives are not the target here — the technique relies on characteristics specific to flash storage and its controllers.

Mitigations are awkward. Coarsening timers further would degrade legitimate web performance APIs that developers depend on. Restricting background tab execution helps but does not eliminate the channel. The cleaner fix sits at the browser-engine level, in how JavaScript is allowed to observe shared system resources, and that work tends to move slowly.

For defenders, the practical exposure is limited for now. FROST is a research result, not a tool circulating on criminal forums, and translating a lab classifier into reliable attacker infrastructure is non-trivial. Privacy-sensitive environments — newsrooms, law firms, anything doing source protection — should note it anyway. Browser hardening guides that already recommend closing tabs, isolating sessions, and using separate profiles for sensitive work apply cleanly here.

Expect Chrome, Firefox, and Safari teams to look at timer precision in storage-adjacent APIs in upcoming releases. Whether that closes the channel or just narrows it is the open question.