SecurCheckCyber Center
Need help
Back to analysis tools
All cyber threats
Accounts & identity

Cookie theft

Cookie theft

Cookie theft copies browser-stored values; a valid session cookie may enable impersonation if the service lacks sufficient session protections.

Fiche de sensibilisationPrête à diffuser à vos équipes ou clients

MIGHT YOU BE AFFECTED?

Turn knowledge into action.

How does this work?

After sign-in, a service associates browser requests with a session cookie. An infostealer, compromised browser extension or application vulnerability may expose that cookie. Replaying it can provide access to an already authenticated session even if MFA protects initial sign-in. HttpOnly, Secure and SameSite mitigate certain exposure paths but cannot stop every endpoint compromise.

REAL-WORLD EXAMPLE

« An employee installs a malicious browser extension. Soon afterwards, unfamiliar mailbox views and downloads appear without a new MFA prompt. »

Typical sequence

  1. 1Compromise a browser or gain access to its storage.
  2. 2Extract cookies from the browser profile.
  3. 3Identify cookies linked to active sessions.
  4. 4Attempt replay against the corresponding services.
  5. 5Access accounts if session controls fail to prevent replay.

Warning signs

  • Unrecognised sessions or account actions.
  • Unusual access without a fresh MFA challenge.
  • Recently installed extensions with excessive permissions.
  • Unexpected bulk downloads or sensitive changes.
  • EDR warnings or infostealer indicators on the endpoint.

How to protect yourself

  • Protect browser cookies and revoke compromised server-side sessions.
  • Use EDR, browser patching and controlled extensions.
  • Configure HttpOnly, Secure and SameSite for the application.
  • Limit session lifetime and support server-side revocation.
  • Require phishing-resistant reauthentication for sensitive actions.
  • Monitor session, device and data-access anomalies.
  • Restrict unapproved software on endpoints.

If you think you are affected

From a trusted device, revoke affected sessions and tokens, then change potentially exposed credentials. Isolate and investigate the suspected endpoint, remove the compromise source, examine logs and determine which data was accessed. A password change alone does not necessarily revoke active sessions.

Get help

Last updated: 8 October 2026