Infostealers and stolen session cookies: why basic breach monitoring falls short

Infostealer logs leak live session cookies that bypass MFA, which breach-list checks miss. How the attack works and how to harden sessions in apps you build.

TechLogHub Engineering Team
April 6, 2026
3 min read
0 views

Share Article

Why Simple Breach Monitoring Is No Longer Enough

Checking whether employee emails appear in breach dumps was once a reasonable baseline. Infostealer malware has changed the problem: instead of old passwords from a third-party breach, attackers now buy fresh logs containing saved credentials and live session cookies straight from infected browsers. A stolen session cookie skips the login page, and therefore skips MFA. For developers, that makes session design, not only password policy, a security control.

What happened

In an April 2026 sponsored article on BleepingComputer, Ran Geva, CEO of Webz.io and its dark-web monitoring service Lunar, argued that breach-list monitoring misses most of today's credential risk. The figures come from Lunar's own commissioned survey and data, so treat them as vendor research: 85% of respondents rated stolen credentials a high or very high risk, but only 32% used dedicated credential monitoring tools and 17% had none. Lunar says it observed 4.17 billion compromised credentials in 2025 and names stealer families including LummaC2, Rhadamanthys, Vidar and Acreed on Windows and AMOS, Odyssey and MacSync on macOS.

The underlying trend is well documented outside vendor marketing. In May 2025, Microsoft's Digital Crimes Unit, the US Department of Justice, Europol and Japan's JC3 disrupted the Lumma Stealer operation, taking down or blocking about 2,300 malicious domains after Microsoft identified more than 394,000 infected Windows computers in two months. On the defence side, Google made Device Bound Session Credentials (DBSC) generally available in Chrome 146 on Windows in April 2026, specifically to make stolen session cookies useless.

Who is affected

  • Organisations whose staff use personal or unmanaged devices to reach SaaS apps, where endpoint protection and device compliance do not apply.
  • Developers, whose browsers often hold sessions for GitHub, cloud consoles, CI systems and package registries.
  • SaaS builders, whose users' sessions can be replayed by attackers if sessions are long-lived and not bound to a device.

What it means for developers and engineering teams

An infostealer attack usually follows four steps. A device is infected through a cracked app, malicious ad, fake browser extension or poisoned download. The stealer copies browser-saved passwords, cookies and autofill data and sends them to the operator. The logs are sold on markets or Telegram channels. A buyer imports the cookies into their own browser and is logged in as the victim, with no password or MFA prompt, often from a different country.

Breach monitoring based on combo lists detects none of this until long after the fact. What helps is making sessions harder to replay and quicker to kill:

  • Short session lifetimes with refresh, and step-up re-authentication for sensitive actions (changing email, creating API tokens, payouts).
  • Session binding. DBSC ties a session to a hardware-backed key on the device, so a copied cookie expires quickly and cannot be refreshed elsewhere. Sites need to implement the DBSC registration and refresh endpoints to benefit.
  • Anomaly checks on session reuse: a sudden change of IP range, ASN, country or user agent mid-session is a strong signal.
  • Revocation that works. If you use stateless JWTs, you need a revocation list or short expiry, or you cannot kill a stolen session.

Cookie attributes do not stop a stealer running on the user's own machine, but they close other theft paths and are cheap to get right:

Set-Cookie: __Host-session=<opaque-id>; Path=/; Secure; HttpOnly; SameSite=Lax; Max-Age=3600

Use an opaque, server-side session identifier rather than a long-lived token that carries its own authority, so the server can always say no.

What to do now

  1. Treat infostealer exposure as its own risk, with an owner and a playbook: on confirmed exposure, reset the password, revoke all sessions and tokens, and reimage the device.
  2. Revoke sessions centrally. In Microsoft Entra, Revoke-MgUserSignInSession -UserId [email protected]; in your own app, provide an admin "sign out everywhere".
  3. Shorten sessions for admin and high-risk roles and require re-authentication for privileged actions.
  4. Restrict access from unmanaged devices to critical SaaS via conditional access or a browser-isolation policy.
  5. Evaluate DBSC for your web app, and enable cookie protections you already have: Secure, HttpOnly, SameSite and the __Host- prefix.
  6. Feed stealer-log intelligence into your IdP and SIEM so confirmed exposures trigger automatic session revocation rather than a ticket.

Related on TechLogHub

Sources

Stay Updated

Get the next deep dive in your inbox

Subscribe for product analysis, engineering explainers, and practical guides published on TechLogHub.

See what launched this week

One email a week: new and trending developer tools, fresh comparisons, and what shipped. Unsubscribe in one click.