Executive Summary
In June 2026, researchers from Graz University of Technology unveiled a novel side-channel attack named FROST (Fingerprinting Remotely using OPFS-based SSD Timing). This attack enables malicious websites to infer users' browsing habits and application usage by exploiting SSD access time variations through JavaScript, without requiring native code execution or user permissions. By leveraging the Origin Private File System (OPFS) API, attackers can create large files that induce measurable SSD latency changes when other applications or websites are accessed, allowing them to identify specific user activities with high accuracy. (tugraz.elsevierpure.com)
The FROST attack underscores the evolving landscape of web-based privacy threats, highlighting the potential for sophisticated side-channel attacks that operate entirely within the browser environment. As web applications become more complex and integrated with local system resources, the need for robust security measures to mitigate such vulnerabilities becomes increasingly critical.
Why This Matters Now
The FROST attack demonstrates a significant advancement in side-channel techniques, revealing that standard web APIs can be exploited to compromise user privacy without explicit consent. This highlights the urgent need for browser developers and security professionals to reassess and fortify existing defenses against such covert attacks.
Attack Path Analysis
A malicious website exploits the OPFS API to create large files on the user's SSD, enabling it to measure SSD read times and infer user activity. This technique allows the attacker to identify which websites and applications the user accesses without requiring native code execution or user permissions.
Kill Chain Progression
Initial Compromise
Description
The user visits a malicious website that utilizes JavaScript to exploit the OPFS API, creating large files on the user's SSD to measure read times.
MITRE ATT&CK® Techniques
JavaScript
Exploitation for Client Execution
Time Based Evasion
Browser Information Discovery
Local Storage Discovery
Potential Compliance Exposure
Mapping incident impact across multiple compliance frameworks.
PCI DSS 4.0 – Ensure that all system components are protected from known vulnerabilities
Control ID: 6.4.3
NYDFS 23 NYCRR 500 – Cybersecurity Policy
Control ID: 500.03
DORA – ICT Risk Management Framework
Control ID: Article 5
CISA ZTMM 2.0 – Data Protection
Control ID: 3.1
NIS2 Directive – Cybersecurity Risk Management Measures
Control ID: Article 21
Sector Implications
Industry-specific impact of the vulnerabilities, including operational, regulatory, and cloud security risks.
Financial Services
FROST attack enables websites to track financial applications and sites accessed via SSD timing, compromising client confidentiality and regulatory compliance requirements.
Health Care / Life Sciences
Patient privacy at severe risk as malicious sites can track healthcare applications and websites through JavaScript-based SSD timing attacks without permissions.
Computer Software/Engineering
Software development environments vulnerable to intellectual property theft as FROST attack tracks accessed development tools and repositories via SSD contention monitoring.
Legal Services
Attorney-client privilege threatened by FROST's ability to monitor legal research platforms and case management applications through browser-based SSD timing analysis.
Sources
- New FROST Attack Lets Websites Track What Sites and Apps You Open via SSD Timinghttps://thehackernews.com/2026/06/new-frost-attack-lets-websites-track.htmlVerified
- Researchers say they can spy on your browsing by measuring SSD activity through a browser APIhttps://www.tomshardware.com/tech-industry/cyber-security/researchers-say-they-can-spy-on-your-browsing-by-measuring-ssd-activity-through-a-browser-apiVerified
- FROST Side-Channel Attack Spies on Mac Browsing via SSD Latencyhttps://pccentral.net/frosted-side-channel-attack-spies-mac-browsing-ssd-latency/Verified
Frequently Asked Questions
Cloud Native Security Fabric Mitigations and ControlsCNSF
Aviatrix Zero Trust CNSF is pertinent to this incident as it can limit the attacker's ability to exploit the OPFS API for inferring user activity by enforcing strict segmentation and controlled egress policies.
Control: Cloud Native Security Fabric (CNSF)
Mitigation: The attacker's ability to exploit the OPFS API may be constrained by enforcing strict segmentation policies that limit unauthorized access to sensitive APIs.
Control: Zero Trust Segmentation
Mitigation: The attacker's scope may be limited by enforcing segmentation policies that prevent unauthorized access beyond the browser environment.
Control: East-West Traffic Security
Mitigation: The attacker's ability to move laterally may be constrained by enforcing east-west traffic controls that limit unauthorized internal communications.
Control: Multicloud Visibility & Control
Mitigation: The attacker's ability to establish covert channels may be limited by implementing visibility and control measures that detect and restrict unauthorized data flows.
Control: Egress Security & Policy Enforcement
Mitigation: The attacker's ability to exfiltrate data may be constrained by enforcing egress policies that monitor and control outbound data flows.
The attacker's ability to compromise user privacy may be limited by implementing comprehensive security controls that monitor and restrict unauthorized data access and exfiltration.
Impact at a Glance
Affected Business Functions
- User Privacy
- Data Security
- Regulatory Compliance
Estimated downtime: N/A
Estimated loss: N/A
Potential exposure of user browsing habits and application usage patterns.
Recommended Actions
Key Takeaways & Next Steps
- • Implement browser-level restrictions on the OPFS API to prevent unauthorized file creation and access.
- • Enhance browser security features to detect and block side-channel attacks exploiting hardware timing variations.
- • Educate users about the risks of visiting untrusted websites and the potential for side-channel attacks.
- • Develop and deploy browser patches that mitigate the ability to measure SSD read times through JavaScript.
- • Collaborate with hardware manufacturers to design SSDs that are less susceptible to timing-based side-channel attacks.



