top of page

Browser-Based Attacks: Defending Enterprises Against Malicious Extensions and Session Theft

4 days ago
6 min read

MINAKSHI DEBNATH | DATE: November 10,2026



We’ve spent the last decade perfecting the enterprise identity perimeter. Multi-factor authentication (MFA) and FIDO2 passkeys are practically industry standard now. But let's be brutally honest for a second. Threat actors aren't trying to break down the front door anymore. They’re simply walking in through the window your web browser.

As we migrate core workflows to SaaS and cloud providers, the browser has become the de facto operating system for most knowledge workers, a shift highlighted in Google's analysis on protecting cookies. According to Guardz's guide for MSPs, adversaries have recognized this shift. Instead of dropping traditional binary payloads, threat actors are pivoting to browser-centric exploitation, as detailed by Packetlabs's analysis on session hijacking.

Why fight MFA when you can just steal an active session?


The Cookie Theft Arms Race


Once a user successfully authenticates, the browser holds onto long-lived bearer tokens mostly HTTP cookies. If an infostealer snatches those cookies, an attacker halfway across the globe can bypass MFA entirely, a threat vector Google Chromium's post on fighting cookie theft warns is rapidly escalating.

Historically, browsers relied on OS-level protections. But as Devoteam's research on DPAPI limitations points out, the traditional Windows Data Protection API (DPAPI) had a fatal flaw. Any process running under the logged-in user's context could simply ask the operating system to decrypt those secrets. Infostealers like LummaC2 and Vidar capitalized heavily on this open door.

Google tried to slam this shut in Chrome 127 with App-Bound Encryption (ABE). According to Kaspersky's research on the VoidStealer Trojan and Zscaler's breakdown of Chrome's App-Bound Encryption, this new architecture binds the master encryption key to the actual identity of the Chrome executable. It uses a system-level Windows service to verify the caller's digital signature and binary path before handing over decrypted keys.


Early implementations even suffered from path canonicalization vulnerabilities, tracked as CVE-2025-34092 on GitHub, allowing unprivileged malware to trick the service. But sophisticated malware quickly adapted by turning the browser against itself entirely.

Take the recent "Abe Office" campaign. According to Brandefense's threat report on Abe Office malware, attackers now bypass these protections through in-process injection. The malware executes a legitimate, hidden Chrome process off-screen sometimes pushing it to extreme display coordinates like -32000,-32000.


Next, it injects a malicious DLL directly into that authentic Chrome process. Operating from inside the trusted browser memory, the malware asks the ABE service to decrypt the keys. The system sees a signed, legitimate Google binary making the request and approves it. Another variant, as reported in SecurityWeek's analysis of Glove Stealer, similarly bypasses App-Bound Encryption to access these protected stores.

Your cookies are exfiltrated, and your MFA is officially bypassed. Attackers are no longer stealing passwords to log in; they are stealing the browser's memory to bypass the login entirely.


When the Browser Goes Rogue: APT Extensions


While ransomware affiliates hunt for session cookies, Advanced Persistent Threat (APT) groups like Kimsuky highlighted in CISA's advisory on North Korean APTs deploy malicious browser extensions to turn the user agent into a persistent surveillance tool.

Volexity's deep dive into the SHARPEXT extension reveals a terrifying post-exploitation tactic targeting organizations across the US, Europe, and South Korea, according to Infosecurity Magazine's coverage of North Korean hackers. Rather than stealing a password, which tends to set off geo-velocity IP alerts or step-up MFA prompts, SHARPEXT simply piggybacks on the user’s active session.


To install it without tripping Chrome’s anti-tampering warnings, the attackers use custom VBScripts that recalculate the cryptographic hashes in the browser’s Secure Preferences file offline. Once loaded, the extension watches webmail activity, parses the page’s internal Document Object Model (DOM) structures, and quietly uploads sensitive emails in the background.

A few of the changes, in case you want to adjust them: “silently rides on” became “piggybacks on” for a more conversational feel, “often triggers” became “tends to set off” to vary the verb, and “manually recalculate” was trimmed to “recalculate,” since “offline” already carries the sense of a hands-on process. I also split the second sentence’s structure slightly so it reads less like a stacked list of actions.

NK News's report on DPRK watchers confirms this extension was heavily deployed against academic and policy researchers.

Similarly, Zscaler ThreatLabz's analysis of TRANSLATEXT shows how these actors use disguised translation utilities to harvest credentials and screen captures dynamically, evading traditional endpoint detection.

The Hardware Fix: Device Bound Session Credentials

We can't rely purely on software to protect software. The industry is actively moving toward a hardware-anchored defense called Device Bound Session Credentials (DBSC).

As detailed in Corbado's technical explanation of DBSC architecture and the official W3C Web Application Security Working Group specifications, this protocol fundamentally changes the security paradigm. It binds authentication sessions to a cryptographic key stored safely inside the device's Trusted Platform Module (TPM 2.0) or macOS Secure Enclave.


The browser uses standard, short-lived bearer cookies for high-frequency network requests. But when those expire usually within minutes the browser must cryptographically prove it holds the physical hardware key to get a refresh token.

If a hacker extracts the cookie and tries to use it on an off-device machine, the server issues a challenge. Lacking the victim's hardware TPM, the remote attacker fails the challenge. The session is immediately terminated. To resolve latency gaps in complex Single Page Applications, Chrome introduced the Device Bound Session Credentials JavaScript API, ensuring synchronous state verification.

According to Google Workspace's admin guide on session binding and recent Google Workspace Updates regarding DBSC, this capability is now becoming a critical requirement for defending enterprise identity tenants.


Hardening the Enterprise: Your Browser Action Plan


Technology like DBSC is the future, but what do we do right now? Defending against these threats requires a heavy hand on policy governance and endpoint telemetry. You need to treat the browser like a highly privileged environment.

The Path Forward


The line between network security, identity management, and the endpoint has entirely vanished. Threat actors have realized that compromising the web browser is the ultimate skeleton key to the modern enterprise.

By enforcing rigid extension policies, tracking advanced telemetry, and preparing for hardware-bound credentials, we can cut off this attack surface at the source.

Explore how AmeriSOURCE and our ecosystem of specialized brands like AQcomply, IronQlad, and AJA Labs can support your zero-trust journey and digital transformation initiatives today.


KEY TAKEAWAYS


  • Infostealers routinely bypass MFA by extracting active HTTP session cookies directly from browser memory, evading traditional login defenses.

  • Advanced malware circumvents Chrome's App-Bound Encryption by injecting malicious DLLs into legitimate, hidden browser processes to act as a decryption oracle.

  • APT groups utilize malicious browser extensions to silently hijack authenticated sessions, harvesting emails and DOM data without triggering identity alerts.

  • Enterprises must transition to Device Bound Session Credentials (DBSC) to anchor web sessions to hardware TPMs, neutralizing off-device cookie theft.

  • IT leaders should enforce a strict ExtensionSettings JSON policy to block unapproved extensions globally and restrict access to critical browser APIs.

 

 
 
 

Comments


bottom of page